I am aware that this function would only work reliably if you use AS clauses. But that's what I intend to do, so no problem. Sorry for not having mentioned that.
So is this the reason that the function doesn't exist? That it needs AS clauses to be useful? Or the efficiency pitfall I suspected? Or both? Or something else? No big problem, I can work with sqlite3_column_name. It would just have been more convenient to have the reverse function, too. Sebastian On Mon, 3 Sep 2018 07:27:23 +0000 Hick Gunter <h...@scigames.at> wrote: > The name of an output column is not even defined, much less unique, unless > the author of the statement has done extra work (using unique column names > and/or AS clauses). > > Consider > > Select a.*,b.*,c.* ... > > Where each table has a column named Id. Which index would you like to have > returned? > > -----Ursprüngliche Nachricht----- > Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im > Auftrag von Sebastian > Gesendet: Sonntag, 02. September 2018 16:14 > An: sqlite-users@mailinglists.sqlite.org > Betreff: [EXTERNAL] [sqlite] Missing function sqlite3_column_index > > Hi, > for sqlite3_bind_parameter_name there is an inverse function > sqlite3_bind_parameter_index. > But for sqlite3_column_name, I could not find such a function. > > Is it missing by intention, in order not to tempt users to call it once per > row, which would be inefficient? > (In that case, why not just mention that in the documentation?) _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
