From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ari King <ari(dot)brandeis(dot)king(at)gmail(dot)com> |
Cc: | "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
Subject: | Re: Fwd: Timestamp Query Parameters |
Date: | 2014-03-13 22:32:47 |
Message-ID: | 5322320F.5080107@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 03/13/2014 03:30 PM, Ari King wrote:
> Probably should have mentioned before:
>
> mogrify(operation[, parameters])
>
> Return a query string after arguments binding. The string
> returned is exactly the one that would be sent to the database
> running the execute() method or similar.
>
> So mogrify does not actually run against the database. I was
> assuming you where doing an execute() later which may be an
> erroneous assumption. To use parameters in execute() see here:
>
> http://initd.org/psycopg/docs/usage.html#passing-parameters-to-sql-queries
>
>
> Thanks for the clarification. I was successful in using mogrify wrapped
> in execute. Passing parameters to SQL queries via execute still won't
> work for me though. Thoughts?
Crank up the statement logging in postgresql.conf to 'all' and see what
is actually hitting the database.
>
> -Ari
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Lutz Steinborn | 2014-03-14 05:40:31 | Re: Fwd: Timestamp Query Parameters |
Previous Message | Adrian Klaver | 2014-03-13 22:17:54 | Re: Fwd: Timestamp Query Parameters |