Re: Array of composite types returned from python - Mailing list pgsql-hackers

From Sim Zacks
Subject Re: Array of composite types returned from python
Date
Msg-id 1440287423.479.1403984483224.JavaMail.root@compulab.co.il
Whole thread Raw
In response to Array of composite types returned from python  ("Behn, Edward (EBEHN)" <EBEHN@arinc.com>)
Responses Re: Array of composite types returned from python  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
List pgsql-hackers

Am I missing anything, (ie memory leak, undesirable behavior elsewhere)? 

-Ed 


I applied the patch and it looks like it is working well. As a longtime plpython user, I appreciate the fix.

I have a few comments:
1) I would remove the error message from the PO files as well.

2) You removed the comment:
-            /*
-             * We don't support arrays of row types yet, so the first argument
-             * can be NULL.
-             */

But didn't change the code there. 
I haven't delved deep enough into the code yet to understand the full meaning, but the comment would indicate that if
arraysof row types are supported, the first argument cannot be null.
 

3) This is such a simple change with no new infrastructure code (PLyObject_ToComposite already exists). Can you think
ofa reason why this wasn't done until now? Was it a simple miss or purposefully excluded?
 



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal (9.5) : psql unicode border line styles
Next
From: "MauMau"
Date:
Subject: Re: [Fwd: Re: proposal: new long psql parameter --on-error-stop]