Not sure if it will make a difference, but in your trigger stuff you explicitly coded null for the primary key value. Have you tried changing that so that you don't specify the primary key field at all? I can't remember from the previous post, but I think it was (or should be) set up as autoincrement.
I think SQLite allows using multiple nulls for the primary key, but according to their docs, it is non-standard and it says something about "this may change in the future". Maybe you are getting caught in the middle of a change that is going to occur across multiple revisions of SQLite. Jim On 3/24/09, Damien Elmes <reso...@ichi2.net> wrote: > Sorry, my application's files are called decks, and I unwittingly used > the wrong terminology. > > Any ideas about the problem? > > On Sat, Mar 21, 2009 at 2:27 AM, Griggs, Donald > <donald.gri...@allscripts.com> wrote: >>>>>> >>>>>>> However, when I ask the user to send me their deck, I find that: >>>>>>> >>>>>>> sqlite> pragma integrity_check; >>>>>>> integrity_check >>>>>>> --------------- >>>>>>> ok >>>>>>> sqlite> select id, count(id) from cards group by id having >>>>>>> count(id) >>>>>>>> 1; >>>>>>> sqlite> >>>>>>> >>>>>>> Any ideas? >> >> Obviously, that user is not playing with a full deck. ;-) >> >> >> _______________________________________________ >> 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 > -- Software first. Software lasts! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
