Simon Slavin-3 wrote: > > > I agree with Jay. What's happening is this: > > New row assembled. > Attempt to INSERT new row (first attempt) > INSERT fails UNIQUE contraint. > Notes that it was an INSERT OR REPLACE, therefore ... > DELETE original row. > Attempt to INSERT new row (second attempt) > INSERT works. > > It might go around the loop more than once but it's something like that. >
Thank you all, you're definitely right... there was another primary key, even if I was quite sure that it wasn't configured in that way. Removing it, everything worked fine. Thanks again, Livio -- View this message in context: http://old.nabble.com/Multi-column-unique-constraint-in-SQLite-tp32441748p32446094.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
