From: | Theo Kramer <theo(at)flame(dot)co(dot)za> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Hardus Havenga <hardus(at)flame(dot)co(dot)za> |
Subject: | Re: BUG #1178: PQexecPrepared - PostgreSQL 7.4.1 |
Date: | 2004-06-24 13:42:46 |
Message-ID: | 1088084566.4178.8.camel@dhcp3.coza.net.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 2004-06-22 at 19:23, Tom Lane wrote:
> "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> > PQexec(conn,
> > "PREPARE S0000123_000 (text) AS SELECT * from test1 WHERE t = $1");
> > When invoking PQexecPrepared() I get the following message from the backend
> > ERROR: prepared statement "S0000123_0000" does not exist
>
> Case sensitivity. PQexecPrepared takes its name argument literally,
> but anything inside a SQL command will get downcased unless quoted.
> So you actually prepared "s0000123_000".
>
Many thanks - perhaps a gotcha in the documentation for PQexecPrepared()
would useful...
Regards
Theo
From | Date | Subject | |
---|---|---|---|
Next Message | Hebert, Caroline | 2004-06-24 13:56:04 | ECPG doesn't return the correct length for an empty |
Previous Message | Kris Jurka | 2004-06-24 12:32:32 | Dump/Restore of cvs regression database gives invalid timestamp syntax error |