Why are you putting () around the fields? Is that even legal in SQL for a SELECT field list? It sounds like you're dismissing libraries because of a few uncommon edge cases. Which makes me wonder if your main goal is to pass judgement on the libraries rather than finding something that'll work good enough in an application.
You can always file a bug report if you think the library is incorrect, or search the library's mailing list to see if it has been reported before and what the developers' attitude is. On Thu, Mar 31, 2011 at 12:48 PM, Mark McWiggins <[email protected]> wrote: > It may work if coded carefully around its bugs. The most egregious example I > found was that instead of > returning a tuple with the field values expected after doing > SELECT (field1, field2, field3) from table > it returns the STRING with those fields in it, for example > '(8,"just a second, dammit",9)' > that has to be unpacked programmatically. This happens in both psycopg and > psycopg2. -- Mike Orr <[email protected]>
