From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
Cc: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: error messages without schema name |
Date: | 2006-12-13 16:44:01 |
Message-ID: | 8360.1166028241@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"=?UTF-8?Q?Filip_Rembia=C5=82kowski?=" <plk(dot)zuber(at)gmail(dot)com> writes:
> I heard from my PostgreSQL teacher, that all such messages should be
> corrected in the source code, to include schema name too.
I doubt we'd ever do that, because in most scenarios it'd just be
unnecessary clutter, and the primary error messages are supposed to
be kept short.
What probably should happen someday is to add additional fields to error
reports that carry object name, schema name, and so forth. I think
these wouldn't be displayed normally but you could always turn on
"verbose" mode if you needed to see them. This approach is needed to
support applications that want to know, for example, which constraint
failed during an INSERT without having to try to extract it from the
possibly-translated message text.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lenorovitz, Joel | 2006-12-13 16:50:23 | Pltcl error - could not create "normal" interpreter |
Previous Message | Tomi N/A | 2006-12-13 16:43:34 | Re: grant select on all tables of schema or database |