Bug about 'Foreign Key'

From: "Cid R Andrade" <crandrade(at)opeco(dot)com(dot)br>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Bug about 'Foreign Key'
Date: 2001-03-27 14:43:32
Message-ID: 00dc01c0b6cc$4c9e4bc0$543c620a@catnet.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PostgreSQL Developers,

I have a PostgreSQL 7.0.2 running at Conectiva Linux, with kernel 2.2.14, with 56 Mb of data.

I'd created a table:
Create Table Andamento (
Etiqueta integer not null,
CodTecnico integer not null,
DtInicio timestamp not null,
DtLiberacao timestamp null,
Primary Key (Etiqueta),
Foreign Key (Etiquetas) References Etiquetas (Etiqueta) On Delete Cascade)

I wrong a field name in Foreign Key declaration, and PostgreSQL created it!
Before this, I always named triggers and constraints, but, at this time, I'd tried this way.
Well, look the trigger at table Etiquetas:
CREATE CONSTRAINT TRIGGER "<unnamed>" AFTER DELETE ON "etiquetas" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'andamento', 'etiquetas', 'UNSPECIFIED', 'etiquetas', 'etiqueta');

It says exists a field named etiquetas at table Andamento.
I'd droped table andamento (Drop Table Andamento) and the trigger referencing it didn't droped.

I solved it with pg_dump.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-03-27 15:34:30 Re: Please help On Alternative Database Location
Previous Message Karel Zak 2001-03-27 10:35:57 Re: Wrong formated date on the first day of the Daylight Saving time.