From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Cc: | Richard Harley <raharley0(at)googlemail(dot)com>, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Subject: | Re: Psycgop1 vs Psycopg2 |
Date: | 2011-01-14 16:27:30 |
Message-ID: | 201101140827.30624.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Friday 14 January 2011 5:58:42 am Richard Harley wrote:
> Thanks for your reply Daniel.
>
> The escaped characters are causing problems for instance in this query:
>
> INSERT INTO REGISTER (studentid, code) VALUES ('5632', '\')
>
> In psycopg1 this works perfectly. In psycopg2 the \ escapes the next
> character and causes a syntax error at the postgres level. At least this is
> what I think is happening.. the versions of postgres I am testing on are
> the same - 8.1, and Zope above that. I am concerned that altering how
> postgres escapes characters would cause problems elsewhere. Do you advise
> to upgrade to psycopg2 in production environment ?
> Thanks
> Richard
> On Thu, Jan 13, 2011 at 6:15 PM, Daniele Varrazzo <
>
Honestly this is not enough to go on. What is needed per Danieles previous post:
1) The query.
2) The arguments/parameters to the query and method used the pass them to the
query
3) What you expected to show up in the database
4) What did show up in the database if anything.
5) The status of standard_conforming_strings. In 8.1 though it was just
informational and did not actually do anything.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2011-01-14 16:38:57 | Re: Please help fixing a couple of zope-related issues |
Previous Message | Federico Di Gregorio | 2011-01-14 15:38:45 | Re: Please help fixing a couple of zope-related issues |