Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

Jay, Every system that uses a database must deal with this problem, and there are no real easy answers. But here are a few deeper points to consider ... Beautifully written!! Malcolm ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

Very well said. Harold Wood & Meyuni Gani -Original Message- From: Jay A. Kreibich Sent: Sunday, June 14, 2009 8:44 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

On Sat, Jun 13, 2009 at 11:42:21PM +0100, Simon Slavin scratched on the wall: > Do any of you have experience with doing this ? Are there some > conclusive points which will make me decide immediately that I should > do it one way or the other ? I accept reasoned argument, URLs, >

Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

On 14 Jun 2009, at 12:09pm, Kees Nuyt wrote: > [useful stuff] Many thanks for this, which was useful throughout. I'm still interested in anything other people have to say. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

On Sat, 13 Jun 2009 23:42:21 +0100, Simon Slavin wrote: >I'm writing an application which involves lots of relations between >tables. Seen from a high level, my application will have to enforce >lots of rules to ensure database integrity. Before I used SQLite I

[sqlite] Database logic in TRIGGER and CONFLICT, or in software ?

I'm writing an application which involves lots of relations between tables. Seen from a high level, my application will have to enforce lots of rules to ensure database integrity. Before I used SQLite I would have enforced all these rules in my software. But SQLite has lots of ways to