From: | Joel Burton <jburton(at)scw(dot)org> |
---|---|
To: | "V(dot) M(dot)" <txian(at)hotmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Re: unanswered: Schema Issue |
Date: | 2001-04-26 19:32:47 |
Message-ID: | Pine.LNX.4.21.0104261529230.2006-100000@olympus.scw.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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 <jburton(at)scw(dot)org>
Director of Information Systems, Support Center of Washington
From | Date | Subject | |
---|---|---|---|
Next Message | Marc SCHAEFER | 2001-04-26 19:34:09 | Re: Why Size Of Data Backed Up Varies Significantly In SQL 6.5? |
Previous Message | Jie Liang | 2001-04-26 19:29:22 | Re: random rows |
From | Date | Subject | |
---|---|---|---|
Next Message | J.H.M. Dassen Ray | 2001-04-26 19:37:10 | Re: crypt(table.field) ? |
Previous Message | V. M. | 2001-04-26 19:24:02 | Re: Re: unanswered: Schema Issue |