> Haszlakiewicz, Eric wrote:
>> >The prepared statement's name is not a literal, and in general
>> >parameterized queries don't accept parameters beyond literals. So
>> >need to insert the name directly into the SQL command text.
>> Well, that sucks. Now I need to worry about quoting and escaping. :(
>> Is there a limit of what characters can be used in statement names?
>> Neither the docs for PQprepare(), nor the docs for the prepare
>> say anything about that.
>I think the statement's name is an "identifier", just like a table or
>So it has to follow the rules defined for identifiers in the "SQL
> Best regards,
ah.. yes, that makes sense. The syntax for identifiers is relatively
SQL-SYNTAX-IDENTIFIERS), so I _don't_ need to worry about quoting all
that much, just checking for invalid characters. That's much easier.
Thanks for the pointer!
In response to
pgsql-interfaces by date
|Next:||From: Whit Armstrong||Date: 2008-12-09 15:08:35|
|Subject: simple example of copying data from a c/c++ array into postgres|
|Previous:||From: Daniel Verite||Date: 2008-12-03 21:01:02|
|Subject: Re: deallocating prepared statements|