pg_constraint and constraint triggers

Started by Dave Pagealmost 23 years ago4 messageshackers
Jump to latest
#1Dave Page
dpage@pgadmin.org

Hi all,

I couldn't find anything obvious in the archives, but if I dump a
database created in 7.2, then foreign keys are created using CREATE
CONSTRAINT TRIGGER statement. These do not appear to create entries in
pg_constraint in 7.3.x, so as the database is developed further, we end
up with 2 'styles' of fkeys in the catalogues.

This is a pain in pgAdmin III as we we're hoping to use pg_constraint
for simplicity (figuring out the fkeys in 7.2 was always fun :-) ). Is
there any way to get the required entries in the catalog easily, or
should I look at writing some code to generate them (or alternatively,
is there a reason why I shouldn't)?

Regards, Dave.

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Dave Page (#1)
Re: pg_constraint and constraint triggers

"Dave Page" <dpage@vale-housing.co.uk> writes:

I couldn't find anything obvious in the archives, but if I dump a
database created in 7.2, then foreign keys are created using CREATE
CONSTRAINT TRIGGER statement. These do not appear to create entries in
pg_constraint in 7.3.x, so as the database is developed further, we end
up with 2 'styles' of fkeys in the catalogues.

contrib/adddepend/ is supposed to help out with upgrading definitions
loaded from old databases. Possibly you could adapt its logic into
a "fix things" operation in pgAdmin.

regards, tom lane

#3Dave Page
dpage@pgadmin.org
In reply to: Tom Lane (#2)
Re: pg_constraint and constraint triggers

It's rumoured that Tom Lane once said:

"Dave Page" <dpage@vale-housing.co.uk> writes:

I couldn't find anything obvious in the archives, but if I dump a
database created in 7.2, then foreign keys are created using CREATE
CONSTRAINT TRIGGER statement. These do not appear to create entries in
pg_constraint in 7.3.x, so as the database is developed further, we
end up with 2 'styles' of fkeys in the catalogues.

contrib/adddepend/ is supposed to help out with upgrading definitions
loaded from old databases. Possibly you could adapt its logic into a
"fix things" operation in pgAdmin.

Ahh thanks. I had a browse through /contrib but obviously missed that.

Regards, Dave.

#4Andreas Pflug
pgadmin@pse-consulting.de
In reply to: Dave Page (#3)
pgadmin3 wizard snapin technology

was: [HACKERS] pg_constraint and constraint triggers

Dave Page wrote:

It's rumoured that Tom Lane once said:

contrib/adddepend/ is supposed to help out with upgrading definitions
loaded from old databases. Possibly you could adapt its logic into a
"fix things" operation in pgAdmin.

Ahh thanks. I had a browse through /contrib but obviously missed that.

There are a lot of ideas (many implemented in pgadmin2) to enhance pgadmin3 with wizards of all kinds, but currently we don't have a technology to easily snap in additional features. Suggestions? Do we need snapins anyway or should we simply link them into the main project?

Regards,
Andreas