On Sat, 10 Sep 2005, Ned Batchelder wrote: > Rather than overload an existing SQL keyword, would it be possible to > provide pragmas to control the optimizer? Assigning meanings to particular > combinations of SQL queries won't scale as the number of optimizer controls > grows.
I would like to second this opinion. I think a pragma to tell SQLite wether or not 'I realy know what I'm dooing' and want help or not is the preferred method. I don't like the idea of overloading a syntax to have add-on non-obvious implications/meaning. Regards, Mark. > For example, some databases use specially-formatted comments within the SQL > query to control the internals of the system. It isn't portable, but > neither is this new meaning of the CROSS keyword. > > --Ned. > http://nedbatchelder.com > > > -----Original Message----- > From: Kervin L. Pierre [mailto:[EMAIL PROTECTED] > Sent: Saturday, 10 September, 2005 9:08 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] CROSS keyword disables certain join optimizations > > Darren Duncan wrote: > > At 7:25 PM -0400 9/10/05, D. Richard Hipp wrote: > > > > Well, that's fine as long as CROSS still continues to mean and do what > > it has always meant, which is that you explicitly want the result set of > > If I understand the issue correctly, it does. > > "FROM a, b" is usually equivalent to > "FROM a CROSS JOIN b" in most databases. With > the new fix, the first form gives you the > optimized query, whilst the second form turns > it off. But you should get the same results. > > ...I think :) > > Regards, > Kervin > > > > Regards, Mark
