Monday, July 26, 2004, 12:33:41 PM, Roger Reghin wrote: > I also use EMPTY_RESULT_CALLBACKS for the same reason Nuno does. And my > software also needs FULL_COLUMN_NAMES as well. So, no 3.x for me... =(
In 3.x column names are available as soon as the query is prepared. See the C API reference at http://www.sqlite.org/capi3ref.html#sqlite3_column_name > const char *sqlite3_column_name(sqlite3_stmt*,int); > const void *sqlite3_column_name16(sqlite3_stmt*,int); > > The first parameter is a prepared SQL statement. This function returns > the column heading for the Nth column of that statement, where N is > the second function parameter. The string returned is UTF-8 for > sqlite3_column_name() and UTF-16 for sqlite3_column_name16(). In other words, there is no need for the pragma. e > ----- Original Message ----- > From: "Nuno Lucas" <[EMAIL PROTECTED]> > To: "sqlite" <[EMAIL PROTECTED]> > Sent: Monday, July 26, 2004 12:33 PM > Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available >> D. Richard Hipp, dando pulos de alegria, escreveu : >> > The following pragmas are scheduled to be removed in the future: >> > >> > EMPTY_RESULT_CALLBACKS >> > FULL_COLUMN_NAMES >> > SHORT_COLUMN_NAMES >> > COUNT_CHANGES >> > >> >> What would be the equivalent to EMPTY_RESULT_CALLBACKS=TRUE then? >> >> I use it to get the column names list to display in a grid, even when >> the result is empty. I think it is better to the user to see them, even >> if no results are present. >> >> Regards, >> ~Nuno Lucas >> >>
