An INSERT OR UPDATE sure would be nice. What i often do in cases like this is: UPDATE .. WHERE; INSERT .. SELECT .. WHERE NOT EXISTS (SELECT ..);. That's two statements -- if that's a problem, then you should use D. R. Hipp's trigger-based solution. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
- Re: [sqlite] Enforcing uniqueness from multiple indexes Richard Hipp
- Re: [sqlite] Enforcing uniqueness from multiple indexes Wout Mertens
- Re: [sqlite] Enforcing uniqueness from multiple indexes Gerry Snyder
- Re: [sqlite] Enforcing uniqueness from multiple ind... Richard Hipp
- [sqlite] Enforcing uniqueness from multiple in... wout.mertens
- Re: [sqlite] Enforcing uniqueness from multiple indexes R Smith
- Re: [sqlite] Enforcing uniqueness from multiple ind... R Smith
- Re: [sqlite] Enforcing uniqueness from multiple... David Raymond
- Re: [sqlite] Enforcing uniqueness from mult... Wout Mertens
- Re: [sqlite] Enforcing uniqueness from... Nico Williams
- Re: [sqlite] Enforcing uniqueness from multiple indexes Nico Williams