Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-28 Thread Joris Dobbelsteen
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Sabino Mullane Sent: woensdag 28 maart 2007 2:50 To: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers [snip] Much too elaborate

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-27 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Included is a more eloborate example, which has some webby thing at http://www.familiedobbelsteen.nl/printer-test/ (should work). Much too elaborate - I'm sorry, but I don't think anyone here is willing to wade through nearly 900 lines of

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-27 Thread Hannu Krosing
Ühel kenal päeval, E, 2007-03-26 kell 16:05, kirjutas Joris Dobbelsteen: Oracle has choosen to allow constraint enforcement by locking on the parent tuple. In contrast postgres has chosen (historically, see RI triggers) to fail on detecting conflicting newly inserted rows (the cross-check).

[HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-26 Thread Joris Dobbelsteen
At this time Postgresql is unable to guarentee that complex* referencial integrity (RI) constraints can be enforced using standard (read non-C) triggers or SQL. This is an unfortunate side-effect of the MVCC model, as it allows multiple transactions to modify a snapshot of the data at a certain

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-26 Thread Tom Lane
Joris Dobbelsteen [EMAIL PROTECTED] writes: My intention is to expose the functionality to the outside world for general use. This provides means to ensure custom complex constraints can be enforced properly. I hope to push it into 8.3 if possible. You are at least a month too late for 8.3,

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-26 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 As a real-world example where the constraint cannot be enforced in postgresql. For every tuple t in cartridge_change, there must exists a tuple t' in printers with t.id = t'.id, and a tuple t'' in cartridge_types with t.color = t''.color

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-26 Thread Joris Dobbelsteen
-Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: maandag 26 maart 2007 19:52 To: Joris Dobbelsteen Cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers Joris Dobbelsteen [EMAIL PROTECTED] writes: My

Re: [HACKERS] Guarenteeing complex referencial integrity through custom triggers

2007-03-26 Thread Joris Dobbelsteen
[66.207.139.130] said: 5505.0.0 Go away, spammer (in reply to MAIL FROM command) [//] -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: maandag 26 maart 2007 19:52 To: Joris Dobbelsteen Cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Guarenteeing complex referencial