> -----Original Message----- > From: D. Richard Hipp [mailto:[EMAIL PROTECTED] > Sent: Monday, February 28, 2005 12:25 PM > To: sqlite-users@sqlite.org > Subject: RE: [sqlite] ticket 1147 > > On Mon, 2005-02-28 at 11:54 -0700, Robert Simpson wrote: > > Column Name - The name of the column as specified in the > SELECT clause and > > what SQLite already generates > > Base Table - The base table the column came from or NULL if > the column was > > computed > > Base Column - The base column of the table the column came > from or NULL if > > the column was computed > > Catalog - The database the column came from or NULL if the > column was > > computed. > > > > OK. This is progress. Now I understand that people need the > database, > table, and column that resultset values originate from in order to > automatically construct an appropriate UPDATE statement. That makes > sense. > > Wouldn't it be better to provide this information with a new API > rather than depend on a column naming convention? That would avoid > ambiguity in cases where users create dodgy column names that contain > characters like space and '.' If such a new API appears soon, would > people (please!) stop using those short_column_names and > long_column_names pragmas?
Yes absolutely, a new API call would be ideal. I'll stop short of dancing naked in the streets, but I will do a jig in my office. :) Robert
