[pg-sql] - Problem with duplicate table (PostgreSQL 7.2.3

I have to duplicate a table to save different instances of datas.

Structure de la table "spectacle"
-------------------------------------------------------- */
CREATE TABLE "spectacle" (
id_spectacle SERIAL,
"id_membre_adherent" INTEGER NOT NULL,
"id_genre_festival" INTEGER,
"id_festival" INTEGER,
"nom" VARCHAR(255),
"compagnie_interprete" VARCHAR(255),
"vitaculture" INTEGER NOT NULL,
"regionales" INTEGER NOT NULL,
"presentation" TEXT,
"genre_precision" VARCHAR(255),
"duree" VARCHAR(255),
"photo1" VARCHAR(255),
"photo1_credit" VARCHAR(255),
"photo2" VARCHAR(255),
"photo2_credit" VARCHAR(255),
"salle" TEXT,
"tarifs" TEXT,
"id_traitement" INTEGER DEFAULT 1,
"distribution" TEXT,
"type_public" VARCHAR(255),
PRIMARY KEY("id_spectacle"),
FOREIGN KEY ("id_festival") REFERENCES "festival"("id_festival")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_genre_festival") REFERENCES
"genre_festival"("id_genre_festival")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_membre_adherent") REFERENCES
"membre_adherent"("id_membre_adherent")
ON DELETE CASCADE
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_traitement") REFERENCES "traitement"("id_traitement")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE
) WITH OIDS;

CREATE INDEX "adherant_spectacle_fk" ON "spectacle"
USING btree ("id_membre_adherent");

CREATE INDEX "genre_spectacle_fk" ON "spectacle"
USING btree ("id_genre_festival");

CREATE INDEX "spectacle_au_festival_fk" ON "spectacle"
USING btree ("id_festival");

When I duplicate this code in an other table named spectacle_v without
Foreygn key ... all is running.

But when I try to delete a spectacle_membre, linked value in spectacle
are correctly deleted, but I have an error for spectacle_v which is not
linked :

(ERROR: referential integrity violation - key in membre_adherent still
referenced from spectacle_v )

I do not understand this message error, because any foreign key is
referenced with this table.

On Fri, 8 Aug 2003, BenLaKnet wrote:

> When I duplicate this code in an other table named spectacle_v without
> Foreygn key ... all is running.
>
> But when I try to delete a spectacle_membre, linked value in spectacle
> are correctly deleted, but I have an error for spectacle_v which is not
> linked :
>
> (ERROR: referential integrity violation - key in membre_adherent still
> referenced from spectacle_v )

What triggers are defined on membre_adherent?

No trigger

Just triggers for foreign key in spectacle and none in spectacle_v

How is it possible to verify triggers for foreign keys ?

Stephan Szabo a écrit:

>On Fri, 8 Aug 2003, BenLaKnet wrote:
>
>
>
>>When I duplicate this code in an other table named spectacle_v without
>>Foreygn key ... all is running.
>>
>>But when I try to delete a spectacle_membre, linked value in spectacle
>>are correctly deleted, but I have an error for spectacle_v which is not
>>linked :
>>
>>(ERROR: referential integrity violation - key in membre_adherent still
>>referenced from spectacle_v )
>>
>>
>
>What triggers are defined on membre_adherent?
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
>
>

No trigger

Just triggers for foreign key in spectacle and none in spectacle_v

How is it possible to verify triggers for foreign keys ?

Stephan Szabo a écrit:

>On Fri, 8 Aug 2003, BenLaKnet wrote:
>
>
>
>>When I duplicate this code in an other table named spectacle_v without
>>Foreygn key ... all is running.
>>
>>But when I try to delete a spectacle_membre, linked value in spectacle
>>are correctly deleted, but I have an error for spectacle_v which is not
>>linked :
>>
>>(ERROR: referential integrity violation - key in membre_adherent still
>>referenced from spectacle_v )
>>
>>
>
>What triggers are defined on membre_adherent?
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
>
>

On Mon, 11 Aug 2003, [ISO-8859-1] Benot Bournon wrote:

> No trigger
>
> Just triggers for foreign key in spectacle and none in spectacle_v
>
> How is it possible to verify triggers for foreign keys ?

Generally a select on pg_trigger. Each foreign key should have 3
triggers, 1 on the referencing table and 2 on the referenced. You find the
tables involved by crossreferencing tgrelid against the oid of the row
in pg_class.

Can you send the results of a pg_dump -s?

we make a dump before ... and with a product pgmanager (ems tech) we do
not show any foreign keys.

But I think all of triggers of referenced table are not deleted.

We recreate the schemas ... and now is running.

How is it possible to identify Triggers with no referenced tables ?

Stephan Szabo a écrit:

>On Mon, 11 Aug 2003, [ISO-8859-1] Beno?t Bournon wrote:
>
>
>
>>No trigger
>>
>>Just triggers for foreign key in spectacle and none in spectacle_v
>>
>>How is it possible to verify triggers for foreign keys ?
>>
>>
>
>Generally a select on pg_trigger. Each foreign key should have 3
>triggers, 1 on the referencing table and 2 on the referenced. You find the
>tables involved by crossreferencing tgrelid against the oid of the row
>in pg_class.
>
>Can you send the results of a pg_dump -s?
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
>