| From: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
|---|---|
| To: | Lista dyskusyjna pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
| Subject: | strange "not deferrable" behaviour |
| Date: | 2003-11-17 13:59:19 |
| Message-ID: | 3FB8D437.4050902@klaster.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Hi
I've got some tables defined as:
create table xx (
some_column references master_table
It means this column is defined by default:
NOT DEFERRABLE, INITIALLY IMMEDIATE
I tried replacing rows in this table by new ones as:
set autocommit=off;
begin;
set constraints all deferred;
delete from ....
insert ...
insert...
commit;
I get "integrity violation"... just after "delete"
If I well understood manual, it works like it should. I'm not sure,
because if I run this query in pgAdmin2, it works fine (why?) and
replaces rows as needed.
When I drop this foreign key constraint (not too easy without a
constraint name) and recreate it as "DEFERRABLE", this query works fine
also in psql.
My question is: Why my query works fine when using pgAdmin, and it fails
when using psql?
Regards,
Tomasz Myrta
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yasir Malik | 2003-11-17 14:10:37 | Re: Addition and subtraction on BIT type |
| Previous Message | Tomek | 2003-11-17 13:51:58 | strange DEFERRABLE behaviour |