Comments on: Python, PostgreSQL, and psycopg2′s Dusty Corners http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/ Made with only the finest 1's and 0's Thu, 26 Jan 2012 21:20:45 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Jay Freeman (saurik) http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/comment-page-1/#comment-51869 Jay Freeman (saurik) Sun, 16 Jan 2011 11:49:42 +0000 http://www.protocolostomy.com/?p=655#comment-51869 I'd love to have seen the actual error messages you were getting from the select call. It is possible this is a typo just on the website (and that those are not copy/pastes of your attempts), but you are missing the close parenthesis for the function calls in your SQL queries. I’d love to have seen the actual error messages you were getting from the select call. It is possible this is a typo just on the website (and that those are not copy/pastes of your attempts), but you are missing the close parenthesis for the function calls in your SQL queries.

]]> By: m0j0 http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/comment-page-1/#comment-28978 m0j0 Thu, 03 Dec 2009 04:05:25 +0000 http://www.protocolostomy.com/?p=655#comment-28978 I thought the same thing! But what wound up happening was *nothing* was quoted if memory serves. It's not clear to me why a parameterized query would not be properly quoted, but a parameterized function call would. If you call curs.query after a callproc(), it just spits out the parameterized query with the variables bound, and it looks like what I'd expect to see from a parameterized 'execute()'. Baffling. I thought the same thing! But what wound up happening was *nothing* was quoted if memory serves. It’s not clear to me why a parameterized query would not be properly quoted, but a parameterized function call would. If you call curs.query after a callproc(), it just spits out the parameterized query with the variables bound, and it looks like what I’d expect to see from a parameterized ‘execute()’. Baffling.

]]> By: mordaunt http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/comment-page-1/#comment-28933 mordaunt Wed, 02 Dec 2009 18:08:50 +0000 http://www.protocolostomy.com/?p=655#comment-28933 I thought this would get psycopg2 to “just work”, but no such luck. I still had some quoting issues. what were the quoting issues? I thought parameterized queries never have quoting issues? o_O I thought this would get psycopg2 to “just work”, but no such luck. I still had some quoting issues.

what were the quoting issues? I thought parameterized queries never have quoting issues? o_O

]]> By: Steve Williams http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/comment-page-1/#comment-28922 Steve Williams Wed, 02 Dec 2009 14:12:50 +0000 http://www.protocolostomy.com/?p=655#comment-28922 If you haven't already been hit with this, don't stuff arguments into an SQL command: http://xkcd.com/327/ If you haven’t already been hit with this, don’t stuff arguments into an SQL command:

http://xkcd.com/327/

]]> By: m0j0 http://www.protocolostomy.com/2009/12/01/python-postgresql-and-psycopg2s-dusty-corners/comment-page-1/#comment-28911 m0j0 Wed, 02 Dec 2009 10:57:54 +0000 http://www.protocolostomy.com/?p=655#comment-28911 If the 'SQL-bits' can be used without any ORM-like functionality, maybe it's worth a look. If the ‘SQL-bits’ can be used without any ORM-like functionality, maybe it’s worth a look.

]]>