John LeSueur wrote: > The reason [the short_column_names] pragma is important to me is for > compatibility with existing codebases. I have a couple large applications > that run on postgres, that I am porting to a desktop application that will > use sqlite as the backend. I would rather not add as aliases to all of the > selects in these applications, so short_column_names is exactly what I want. > I noticed there was a FIX ME comment to remove those pragmas... >
The intend is to fix SQLite 3.0 so that it generates column names the same way as other database engines. Hence it will (in theory) be compatible and no "AS" aliases will be required.
If somebody can supply me with a consise list of rules for generating column names, that would be exceedingly helpful in making SQLite 3.0 more compatible with other engines.
-- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
