Just did some testing on the "other" databases I have available. This "feature" of SQLite does seem to be unique. I am early in the learning curve on SQLite, and had not found this particular "enhancement" as yet. Nice to know, and avoid!
Looks like to me it is time for a new PRAGMA! I am not well versed on the SQL '9x specifications, so don't know if SQLite is breaking spec's or just breaking "convention." Either way I think it deserves consideration, as it directly impacts cross platform (i.e. database engines) environments. Something I am painfully familiar with. Just never got burned by this particular situation in the past, so was blissfully unaware of the pending potential "all nighters," BUMMER! Fred -----Original Message----- From: Gerard Samuel [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 10:47 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [sqlite] Select statements returned column names On Wednesday 18 February 2004 11:23 am, Gerard Samuel wrote: > On Wednesday 18 February 2004 10:58 am, Ilia Alshanetsky wrote: > > Yes, this is the correct behavior, without the table 'prefix' if you have > > common column names in the result set the data would lost. > > True about common column names. But isn't that where aliases come in??? > E.g. select a.foo as foo1, b.foo as foo2........ > Another question. Can this behaviour be turned off, reverting sqlite, making it more compatible to other databases such as mysql, pgsql, mssql, etc???? ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
