On Mon, 31 Jan 2011 13:16:55 -0500, Scott Hess <sh...@google.com> wrote:
> The FTS3 code mostly passes values directly down to and up from the > underlying tables, so if you bound an integer, it is likely to come > back out as an integer when you query. Just to be clear: In the tests I posted earlier with both 3.7.2 and 3.6.22, INSERTing an INTEGER without parameter binding (which isn’t supported in the shell) resulted in an INTEGER coming back out. The FTS3 columns declared INTEGER indeed seem to behave as regular INTEGER columns in regular, non-MATCH queries (although I did not test to see if affinity would coerce a '1' to INTEGER on insertion). Is this the expected behavior? If so, it is a doc bug; if not, it’s a code bug. (By the way—and way off-topic—I just noticed on my last post that this list removes format=flowed from the Content-Type of mails. Is that intended? It rather uglifies things.) Very truly, Samuel Adam <a...@certifound.com> 763 Montgomery Road Hillsborough, NJ 08844-1304 • United States http://certifound.com/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users