I have an issue with an fts3 table sqlite 3.6.22. I have a PHP script that builds an sqlite3 client database for a ps3 application. Depending on where I run the build the script (Gentoo or Mac OS X) I get a database file that has different semantics for a column declared as an integer pk:
CREATE VIRTUAL TABLE Directors USING fts3(id INTEGER PRIMARY KEY NOT NULL, first_name TEXT NOT NULL, last_name TEXT NOT NULL, show_last_name_first INTEGER DEFAULT 0, normalised_name TEXT NOT NULL, sort_name TEXT NOT NULL, fanships_count INTEGER, image_url VARCHAR(255)); For the database file build on OS X or Windows I need to run: SELECT * FROM Directors WHERE id=1 For the database file built on Gentoo I need to run: SELECT * FROM Directors WHERE id='1' Otherwise I get no results. The script that's building the script is exactly the same, the only thing different is the environment; primarily PHP and Sqlite, but obviously there is the whole underlying OS layer. I don't even know where to begin debugging this (unfortunately I did not write the build script), I suspect it has something to do with PHP settings, but I have little experience with both PHP and Sqlite. The fts documentation page (http://www.sqlite.org/fts3.html) indicates column types are syntactic sugar, which seems relevant, but how can the same script output a string in one case and an integer in another? -- Gabe da Silveira http://darwinweb.net _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
