There have been past discussions asking the same thing and various sqlite
developers saying I'll check and reporting back that FTS3 doesn't implement
replace or ignore.

I was hoping someone had come up with a work around solution since then that
doesn't have a big performance penalty.



Simon Slavin-3 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
> 
> 

-- 
View this message in context: 
http://old.nabble.com/FTS3-IGNORE-OR-REPLACE-----tp26191125p26201803.html
Sent from the SQLite mailing list archive at Nabble.com.

_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to