pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomasz Myrta <jasiek@klaster.net>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Lista dyskusyjna pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: strange "not deferrable" behaviour
Date: Mon, 17 Nov 2003 16:35:07 +0100
Message-ID: <3FB8EAAB.7070603@klaster.net> (raw)
In-Reply-To: <20031117071555.C94696@megazone.bigpanda.com>
References: <3FB8D437.4050902@klaster.net>
	<20031117071555.C94696@megazone.bigpanda.com>

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




view thread (3+ messages)

Message-ID: <3FB8EAAB.7070603@klaster.net>
Permalink:  ../3FB8EAAB.7070603@klaster.net/
Also on:    postgresql.org/message-id/3FB8EAAB.7070603@klaster.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: jasiek@klaster.net, sszabo@megazone.bigpanda.com
  Subject: Re: strange "not deferrable" behaviour
  In-Reply-To: <3FB8EAAB.7070603@klaster.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox