| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: enhanced error fields |
| Date: | 2012-12-28 20:40:48 |
| Message-ID: | 50DE03D0.4000309@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/28/12 2:03 PM, Peter Geoghegan wrote:
> Are you aware of any popular programming language that provides this
> kind of information? Can you tell in a well-principled way what
> function a Python exception originated from, for example? These are
> the built-in Python 2 exception classes:
>
> http://docs.python.org/2/library/exceptions.html
>
> None of the Python built-in exception types have this kind of
> information available from fields or anything.
Sure, OSError has a filename attribute (which I'm sure is qualified by a
directory name if necessary), SyntaxError has filename, lineno, etc.
OSError.filename is essentially the equivalent of what is being proposed
here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2012-12-28 20:46:55 | Re: enhanced error fields |
| Previous Message | Pavel Stehule | 2012-12-28 20:40:44 | Re: enhanced error fields |