On Thu, Apr 10, 2008 at 4:40 PM, Pavan Deolasee
[EMAIL PROTECTED] wrote:
On Thu, Apr 10, 2008 at 7:18 PM, Ivano Luberti [EMAIL PROTECTED] wrote:
I think that's because Postgres does not have deferred constraint checks.
I believe it does. See
Dennis Brakhane wrote:
On Thu, Apr 10, 2008 at 4:40 PM, Pavan Deolasee
[EMAIL PROTECTED] wrote:
On Thu, Apr 10, 2008 at 7:18 PM, Ivano Luberti [EMAIL PROTECTED] wrote:
I think that's because Postgres does not have deferred constraint checks.
I believe it does. See
On Thu, Apr 10, 2008 at 11:29 PM, Dennis Brakhane
[EMAIL PROTECTED] wrote:
I believe it does. See
http://www.postgresql.org/docs/8.3/interactive/sql-set-constraints.html
and the DEFERRABLE keyword in CREATE TABLE.
Or am I missing something here?
Only foreign key contrains checks (and
Richard, I was convinced that it was not necessary to provide detailed
SQL to not introduce any noise in the information I was giving to the list.
Anyway you proved right at last, since trying to sample some sql to make
others able to reproduce the problem we were also able to identify the
On Thu, Apr 10, 2008 at 7:18 PM, Ivano Luberti [EMAIL PROTECTED] wrote:
Anyway I am a little surprised by this thing cause I thought that in a case
like this the habgs should happen only at commit/rollback time.
I think that's because Postgres does not have deferred constraint checks.
They
Hello everybody, I have searched for a long time about this issue but I
was not able to find what is the cause. Maybe because I have not been
able to identify the right keywords.
We are experiencing the following problem using postgres8.3 and postgres8.1
On client1 we execute
begin;
insert
Ivano Luberti wrote:
On client1 we execute
begin;
insert into table1
and a message of correct execution for both statements is returned
On client2 we execute
begin;
insert into table2
and the client receives a correct execution message for the begin stmt
but waits for the insert statement
