On Mon, 31 Jan 2011 13:37:35 -0500, Samuel Adam <[email protected]>
wrote:
> 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).
No coercion is done in the FTS3 table. Using the same FTS3 "Test" table
setup as in my previous mail, again in 3.7.2:
sqlite> INSERT INTO "Test" ("id", "Content", "count") VALUES(
...> '121',
...> 'The "id" and "count" columns were declared INTEGER.',
...> '12321');
sqlite> SELECT typeof("id"), typeof("Content"), typeof("count") FROM
"Test";
typeof("id") = text
typeof("Content") = text
typeof("count") = text
Thus is this table neither animal nor vegetable nor mineral.
sqlite> CREATE TABLE "Normal" ("id" INTEGER);
sqlite> INSERT INTO "Normal" ("id") VALUES ('121');
sqlite> SELECT typeof("id") FROM "Normal";
typeof("id") = integer
Very truly,
Samuel Adam <[email protected]>
763 Montgomery Road
Hillsborough, NJ 08844-1304 • United States
http://certifound.com/
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
