Hello, This is an important question which needs to be considered well. I personally don't care either way but if a decision is to be made it should be for standardisation
Can I ask this question, is it a problem only for the people using a wrapper or is it a problem for people using the API interfaces (including the library in there programs) I would think that the people using SQLITE in the program would be referencing the array the column index or am I off the mark here? regards Greg O ----- Original Message ----- From: "D. Richard Hipp" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 20, 2004 12:12 AM Subject: Re: [sqlite] Select statements returned column names > Gerard Samuel wrote: > > > > If I execute an sql select like -> > > SELECT f.id, f.foo FROM table f; > > The returned data is -> > > f.id f.foo > > 1 hello > > 2 world > > > > Instead of the normal (as in other DBs I've used) > > id foo > > 1 hello > > 2 world > > > > Is this the correct/expected behaviour of sqlite? > > You can always specify your own column names using > an AS clause, of source: > > SELECT f.id AS one, f.foo AS two FROM table f; > one two > 1 hello > 2 world > > SQLite does attach "different" names to the columns > than other database engines. This has been a > persistent source of complaint. The problem comes > up on joins more than anyplace else. > > Question to all: If I modified SQLite to use the > same column naming rules as (say) PostgreSQL, how > much existing code would it break? Is this something > that should be done, even though it is a (slightly) > incompatible change? > > > -- > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
