Re: [GENERAL] updating data but the constraint is set "immediate"

2003-07-01 Thread Rudy Koento
--- Bruno Wolff III <[EMAIL PROTECTED]> wrote: > On Tue, Jul 01, 2003 at 02:35:48 -0700, > Rudy Koento <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've realised that my tables' constraint was set > to > > IMMEDIATE. So, when I update one table, there's > error > > because of referential integri

Re: [GENERAL] updating data but the constraint is set "immediate"

2003-07-01 Thread Bruno Wolff III
On Tue, Jul 01, 2003 at 02:35:48 -0700, Rudy Koento <[EMAIL PROTECTED]> wrote: > Hi, > > I've realised that my tables' constraint was set to > IMMEDIATE. So, when I update one table, there's error > because of referential integrity. Reading the docs, I > read that SET CONSTRAINTS has no effect

Re: [GENERAL] updating data but the constraint is set "immediate"

2003-07-01 Thread Stephan Szabo
On Tue, 1 Jul 2003, Rudy Koento wrote: > I've realised that my tables' constraint was set to > IMMEDIATE. So, when I update one table, there's error > because of referential integrity. Reading the docs, I > read that SET CONSTRAINTS has no effect on IMMEDIATE > (and I've confirmed that by trying

[GENERAL] updating data but the constraint is set "immediate"

2003-07-01 Thread Rudy Koento
Hi, I've realised that my tables' constraint was set to IMMEDIATE. So, when I update one table, there's error because of referential integrity. Reading the docs, I read that SET CONSTRAINTS has no effect on IMMEDIATE (and I've confirmed that by trying it out). Is there anyway I can circumvent t