D. Richard Hipp said:On Mon, 2005-02-28 at 11:12 +0200, Cariotoglou Mike wrote:I understand that this "column names" issue is becoming a pain for the sqlite authors, but OTOH, it is very important for wrapper authors...
Why? Why does anybody care what the column names in the result are? What are the column names used for other than to print a header at the top of a table for human-readable output?
I'll second Dr. Hipp's statement. I have my own wrapper that I've written for internal use and seem to be getting along just fine with column names as they are. I do expect the developer (me, in this case) to be smart enough refer to a column by the same name both when setting the SQL and when retrieving the results set. I'm curious just why you feel that you need something different than that. I can't imagine that I'd take too kindly to a wrapper that thought it knew better than me what I wanted to call the columns.
I'll third Dr. Hipp's statement.
I have my own wrappers (in Perl), made for public consumption, and never had problems with returned column names.
Simply put, the elegant solution for wrapper authors is to always use 'as' to explicitly define the column names you want. You always know how these names map to original table columns because you explicitly said so.
Insisting on using default names all the time is for uber-lazy users.
-- Darren Duncan
