I wrote: > Michael Fuhr <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match