From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Nick Rudnick <joerg(dot)rudnick(at)t-online(dot)de> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [pgsql-general 2011-1-21:] Are there any projects interested in object functionality? (+ rule bases) |
Date: | 2011-02-01 02:33:33 |
Message-ID: | AANLkTikmXgX+Bhn_0=g8h6KHgG-yWFPWKJ=ibKJaBUMo@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 31, 2011 at 5:09 PM, Nick Rudnick <joerg(dot)rudnick(at)t-online(dot)de> wrote:
> Interesting... I remember that some years ago, I fiddled around with
> functions, operators etc. to allow a method like syntax -- but I ever was
> worried this approach would have serious weaknesses -- are there any
> principal hindrances to having methods, if no, can this be implemented in a
> straightforward way?
It would help if you were a bit more specific. Do you mean you want
to write something like foo.bar(baz) and have that mean call the bar
method of foo and pass it baz as an argument?
If so, that'd certainly be possible to implement for purposes of a
college course, if you're so inclined - after all it's free software -
but we'd probably not make such a change to core PG, because right now
that would mean call the function bar in schema baz and pass it foo as
an argument. We try not to break people's code to when adding
nonstandard features.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-02-01 02:36:58 | Re: [pgsql-general 2011-1-21:] Are there any projects interested in object functionality? (+ rule bases) |
Previous Message | Robert Haas | 2011-02-01 02:29:31 | Re: Error code for "terminating connection due to conflict with recovery" |