Message-ID: <3FB8EAAB.7070603@klaster.net>
Date: Mon, 17 Nov 2003 16:35:07 +0100
From: Tomasz Myrta <jasiek@klaster.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; pl-PL;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Lista dyskusyjna pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: strange "not deferrable" behaviour
References: <3FB8D437.4050902@klaster.net>
	<20031117071555.C94696@megazone.bigpanda.com>
In-Reply-To: <20031117071555.C94696@megazone.bigpanda.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit

Dnia 2003-11-17 16:16, Użytkownik Stephan Szabo napisał:
> Hmm, I'd suggest turning on query logging to make sure pgAdmin is doing
> what you expect.

Well, I've already done this. I didn't check query log, but a result by 
selecting rows from modified table.

Anyway I opened a pgAdmin log and didn't find anything special.

I also found something interesting in pgAdmin work. When constraint is 
defined as "NOT DEFERRABLE", I get "OK" only when I execute whole query 
at once. PgAdmin probably executes this query using only one statement - 
it separates each sql command using semicolon delimiter.

If I try to split my query and execute each command separately - I get 
the same "integrity violation" error as in psql.

I tried also change constraint into "DEFERRABLE". Behaviours of psql and 
PgAdmin are the same - query executes fine, doesn't matter whether it is 
executed as single or several statements.

Regards,
Tomasz Myrta