fts3 columns are all implicitly TEXT, no matter how you dress them up. There's already docid as a primary-key alias for rowid.
-scott On Wed, Nov 4, 2009 at 11:03 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 4 Nov 2009, at 5:05pm, sorka wrote: > >> Hmm. Have you actually tried this yourself? >> >> Here's what I get with a simplified example: >> >> CREATE VIRTUAL TABLE keyword using FTS3(programId INTEGER PRIMARY KEY, >> title); >> INSERT OR IGNORE INTO keyword (programId, title) VALUES(3, "A"); >> INSERT OR IGNORE INTO keyword (programId, title) VALUES(3, "A"); >> sqlite> select * from keyword; >> 3|A >> 3|A > > Erm ... I don't use FTS3 or VIRTUAL TABLEs but can someone else tell > me whether this shows a bug for a VIRTUAL TABLE ? > > sorka, instead of using INTEGER PRIMARY KEY, can you try one or both > of these: > > CREATE VIRTUAL TABLE keyword using FTS3(programId INTEGER UNIQUE, > title); > CREATE VIRTUAL TABLE keyword using FTS3(programId INTEGER > AUTOINCREMENT, title); > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
