Re: PL/pgSQL Todo, better information in errcontext from plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
Cc: jimn(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL/pgSQL Todo, better information in errcontext from plpgsql
Date: 2006-10-06 14:40:03
Message-ID: 20591.1160145603@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
>> Why do you need the OID to know exactly what function something is? What's
>> wrong with schema.function(args)?

> oid is simply unique. I can take source code, args and all without parsing.
> It's only one difference. I unlike parsing.

That isn't an adequate reason for pushing an implementation detail into
the user's face. IMHO no error message seen by ordinary users should
mention OIDs at all. A thought experiment: what would you do with the
message if we were to reimplement the system to not use OIDs?

I'm willing to talk about putting a complete specification of the
function (with schema and arg types) into the context line, but you
haven't really made the case why that wouldn't be just clutter for most
people.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-10-06 14:47:17 Re: pg_dump exclusion switches and functions/types
Previous Message Stevenson, Bob 2006-10-06 14:30:51 unsubscribe