yes, but my tables have long names, i've already done as suggested by you. why not have a schema table created for us to extract these info. >From: Joel Burton <[EMAIL PROTECTED]> >To: "V. M." <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: Re: [HACKERS] Re: unanswered: Schema Issue >Date: Thu, 26 Apr 2001 15:32:47 -0400 (EDT) > >On Thu, 26 Apr 2001, V. M. wrote: > >(moving this conversation back to pgsql-general, followups to there) > > > perhaps adding t.tgargs to your view enable me to extract parameters > > that are the related fields > >At SCW, we use a naming convention for RI triggers, to allow >us to easily extract that, and deal with error messages. > >We use: > >CREATE TABLE p (id INT); > >CREATE TABLE c (id INT CONSTRAINT c__ref_id REFERENCES p); > >This allows us at a glance to see in error messages what field of what >table we were referencing. In an Access front end, we can trap this >error message to a nice statement like "You're trying to change a value in >the table "c", using information in table "p", "id", but...") > >If you don't have this, yes, you can look at in >the tgargs, but, given that its a bytea field, it's hard to >programmatically dig anything out of it. > >HTH, >-- >Joel Burton <[EMAIL PROTECTED]> >Director of Information Systems, Support Center of Washington > _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
