Clemens wrote:
$ sqlite3
SQLite version 3.8.3 2014-01-11 12:52:25
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite .header on
sqlite values(1);
(null)
1
sqlite .mode html
sqlite values(1);
Segmentation fault
One runs the risk stumbling upon
Klaas V wrote:
Clemens wrote:
$ sqlite3
SQLite version 3.8.3 2014-01-11 12:52:25
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite .header on
sqlite values(1);
(null)
1
sqlite .mode html
sqlite values(1);
Segmentation fault
One runs the risk
On Wed, Jan 15, 2014 at 6:48 AM, Clemens Ladisch clem...@ladisch.de wrote:
And a NULL column name is considered a bug:
http://www.sqlite.org/cgi/src/info/260587d272
Not so much a bug as undesirable. Note that even with the change
referenced above, sqlite3_column_name() might still return
Hi,
the shell does not always check the return value of sqlite3_column_name()
for being NULL:
$ sqlite3
SQLite version 3.8.3 2014-01-11 12:52:25
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite .header on
sqlite values(1);
(null)
1
sqlite .mode html