From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [INTERFACES] PL/Python: How do I use result methods? |
Date: | 2004-12-17 02:17:43 |
Message-ID: | 13490.1103249863@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
I wrote:
> Michael Fuhr <mike(at)fuhr(dot)org> writes:
>> Any comments on this? The 8.0.0rc1 PL/Python documentation,
>> Section 39.3 "Database Access", still mentions the nrows and
>> status methods, but they don't work. Here's Oliver's original
>> message and my followup:
>> http://archives.postgresql.org/pgsql-interfaces/2004-10/msg00019.php
>> http://archives.postgresql.org/pgsql-interfaces/2004-10/msg00020.php
> It looks like someone #ifdef'd out those sections after observing that
> the PLy_result_methods table isn't used anyplace. Perhaps the place
> where it should have been used got lost in some earlier patch?
> Just out of curiosity, what sort of patch would it take to enable these
> functions? If it's at all nontrivial I'd vote to hold over to 8.1,
> but if it's a line or two of code that got lost at some point, it would
> seem like a reasonable bug fix ...
Comparing the result and plan method types made it pretty obvious how
those methods are supposed to be hooked up, and it was indeed a
one-liner omission in the original source code. So I've fixed it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-17 02:52:33 | Re: Shared row locking |
Previous Message | Christopher Kings-Lynne | 2004-12-17 02:09:26 | Re: Shared row locking |
From | Date | Subject | |
---|---|---|---|
Next Message | Jens Lechtenboerger | 2004-12-17 13:45:49 | Re: Lost updates vs resumable connections/transactions |
Previous Message | Robert Wimmer | 2004-12-16 23:52:39 | plpgsql errorcodes |