Skip site navigation (1) Skip section navigation (2)

misleading (or perhaps confusing) error messages

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: misleading (or perhaps confusing) error messages
Date: 2000-08-31 00:08:42
Message-ID: 200008310008.e7V08gk90036@hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Dave E Martin (xxiii(at)cyberdude(dot)com) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
misleading (or perhaps confusing) error messages

Long Description
When an error is generated as the result of a trigger (or other indirect action) it would be helpful if the error message could somehow indicate the trigger was the cause, rather than the executed statement itself.
<PRE>
for instance:

insert into NAS values (...);
ERROR:  nas_make: Permission denied

</PRE>
While the error message is technically correct, it tends to leave one scratching one's head, until one remembers or realizes that a trigger was involved.
When dealing with a complicated series of statements and/or transactions it may be considerably more difficult to make the required inference from the error message.

Sample Code


No file was uploaded with this report


pgsql-bugs by date

Next:From: Alexei E. KorneyevDate: 2000-08-31 19:46:03
Subject: bugs
Previous:From: Barnes, Sandy (Sandra)Date: 2000-08-30 22:07:10
Subject: RE: [BUG] calling lo_creat()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group