> -----Original Message----- > From: Darren Duncan [mailto:[EMAIL PROTECTED] > Sent: Friday, March 19, 2004 2:29 PM > To: SQLite > Subject: RE: [sqlite] moving from mySQL to SQLite - A guidance request > > > At 9:47 AM -0600 3/19/04, Fred Williams wrote: > >You have raised some vaild concerns for sure. But, the rest of the known > >SQL database universe (Oracle, SQL Server, MySQL, Advantage, > Access(?), and > >etc.) does it the other way round. The only reason I prefer the > change is > >to allow for greater cross platform migration. > > > >If there are those who obviously have a great deal invested in > the current > >implementation, then something like a sticky PRAGMA would be a very good > >solution. This would allow the existing code base be protected, > but future > >migration to be more "industry standard." In the old IBM days > the "c.foo" > >would require a "gray area" in the manual:-) > > If the main issue at hand is cross-database compatability, then there > is a good method that already exists as defined by the SQL standards > - "AS". If one were to use that for every returned column in the > select list then you would have the same result using this on any SQL > database. Moreover, using AS all the time allows a type of > uniformity on selects that contain arbitrary expressions in the > select list, which typically use AS anyway. And for people such as > myself who are inclined to generate our SQL from a data dictionary, > making it generate AS all the time is trivial. Those are some > thoughts. -- Darren Duncan >
And I guess we could just use other databases that actually conform to a wide spread standard and just forget about SQLite. This little "feature" is the only thing keeping me from carrying SQLite implementations beyond "trivial." I guess I spent too many years having to avoid the grey areas in IBM manuals, to want to do that again. Lets see now, I have a multi thousand line SQL based implementation based in another database. I am considering switching platforms. To move to one I basically move the bare SQL over and go. With my other possible platform, I must track down, modify every occurrence of a returned column name to implement "AS", test and debug all this, and... Guess what I'm going to do... Fred --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]