RI Trigger Names

On Mon, 16 Sep 2002, Ian Harding wrote:

I am wondering if there is a TODO to make the names for RI constraints
incorporate the name of the constraint they implement to make it
easier for humans to see what is going on. Something like

RI_myconstraintname_Trigger

instead of

RI_ConstraintTrigger_111633344.

I looked in the TODO list and only found these:

-Make foreign key constraints clearer in dump file
-Make other constraints clearer in dump file

Not specifically, but it might be a good idea to do for 7.4
since it'll also give you some limited control over the firing
order of multiple fk constraints on the same table.

"Ian Harding" <ianh@tpchd.org> writes:

I am wondering if there is a TODO to make the names for RI constraints
incorporate the name of the constraint they implement to make it
easier for humans to see what is going on.

No, there isn't; as of 7.3 it doesn't seem necessary (pg_constraint
table is the thing you'd be looking at).

regards, tom lane

Ian Harding wrote:

I am wondering if there is a TODO to make the names for RI constraints incorporate the name of the constraint they implement to make it easier for humans to see what is going on. Something like

RI_myconstraintname_Trigger

instead of

RI_ConstraintTrigger_111633344.

Doesn't strike me as a good idea, since it'd imply a different
max length of constraint names than NAMEDATALEN.

Jan

I looked in the TODO list and only found these:

-Make foreign key constraints clearer in dump file
-Make other constraints clearer in dump file

Thanks!

Ian

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being
right. #
# Let's break this rule - forgive
me. #
#==================================================
JanWieck@Yahoo.com #