Re: How will I adapt from Pick to Oracle?

I absolutely agree with TurkBear's point. Oracle and other RDBMs allow join query to merge data from different data sources. This is one of the greatest features that are missed by Pick. But SQL database will not do the join for you automatically nor randomly. It only do what you asked it to do. If you do not understand what the command is doing or use the wrong syntax you may got what you do not want. However, you should not blame the database.

It is the common complain from Pick users of the extra nested SQL tables for multi or multi sub values. Actually, RDBMs use a different way to deal with multi valued objects - it use multi attributes instead of multi values inside a single attribute. It is Pick sql-create-table program made such confused conversion. If you like you can change your Pick file from multi value to multi attributes then re-create your SQL table. You will eliminate the nested multi value's table.

YS

TurkBear <noone_at_nowhere.com> wrote in message news:ofchct8e1fpvui2br0hdaf44u86vnvh941_at_4ax.com...
> Where did you get the information that this is how SQL databases ( if
 there are
> such things, rather than RDBMs that are SQL based) do joins...In my
 anaysis of
> the performance of my Oracle stuff, unless I [ and not the RDBMS] have
 made
> some outlandish programming mistake, I never have seen any cartesian
 joins, much
> less huge ones...
>
>
>
>
> Ray DeGennaro <SeeReply-To_at_eaglerock-is.com.invalid> wrote:
>
> >In article <xJbw6.14197$TW.58834_at_tor-nn1.netcom.ca>,
> > "Albert Kallal" <kallal_at_msn.com> wrote:
> >
> >>What was one record, now becomes 3 tables, and two of them are
> >>multi-records. YOU have to work out this relation stuff when doing
> >>updates. The sql engine might enforce RI for you, but that just stops
> >>your code from doing something wrong!
> >
> >And what's even worse is the way SQL databases typically do joins. A
> >big (sometimes HUGE) Cartesian product is formed, and then the rows that
> >don't match are eliminated. So, if you aren't careful, your select can
> >return results that don't really exist in your database.
> >
> >
> >Ray
>
Received on Tue Apr 03 2001 - 09:38:25 CDT