On 9 Jul 2017, at 3:50am, petern <peter.nichvolo...@gmail.com> wrote:
> This is what SQLite 3.19.3 VALUES clause presently does independently of > shell.c. My question would be, is this feature going to produce stable > column names going forward caveat the strange behavior of double quotes. I answered your question twice. Both answers were "no". I don’t know how I can state this any more clearly. > The bug here is how the VALUES logic can't have it both ways. A bug would be a situation where SQLite does not perform the way the documentation says it does. The documentation does not state what column names VALUES leads to, therefore there is no such bug here. Since they are not documented, column names for impromptu results — those not retrieved from a TABLE or VIEW — can be anything, and can change between different versions of SQLite. This is not restricted to the use of double quotes. Do not write code which depends on the result of sqlite3_column_name() for such values. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
