On 2/28/05, Dennis Cote <[EMAIL PROTECTED]> wrote: > Yes, it sure would be better to use an API. > > The second would naturally become sqlite3_column_table(), and the fourth > sqlite3_column_database(). > > Unfortunately, the natural name for the third item, > sqlite3_column_name(), is already used. However, rather than the column > name, it returns the usual column heading. This is sometime the column > name alone, and sometimes the table name and the column name separated > by a period, depending upon the type of query, joined or not, and the > column name pragma settings. It's too bad this wasn't called > sqlite3_column_heading(). > > Anyway, to maintain backwards compatibility the new API should probably > be sqlite3_column_short_name() to match the intent of the > short_column_names pragma. It would always return the short name of the > column. > Dennis Cote
Has anyone looked into providing this or has a ticket been entered? I've been looking forward to something like this since it seemed like the obvious thing to do, but haven't heard a peep about it since. Wrapper writiers are sure to love this. -- Joel Lucsy "The dinosaurs became extinct because they didn't have a space program." -- Larry Niven
