On 14 Feb 2012, at 5:17pm, Simon Slavin wrote: > Yes, the columncount returned will reflect what columns you asked for, even > if the SELECT returns zero rows. So if columncount is zero, either it's not > a SELECT command, or you've somehow managed to make a SELECT which returns > zero rows. At least, that's what it did a few releases ago, and I see no > reason it should have changed.
In the above, I should have typed "or you've somehow managed to make a SELECT which returns zero -->columns<--", not zero rows. Sorry for any confusion, which was unfortunately key to the statement I was trying to make. Also, Stephan is quite right: it's not the columns but the values which have datatypes, and if you're looking at some random SQLite database that wasn't carefully created the value in r1c1 may be an integer but the value in r2c1 may be text. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
