Tom Lane wrote:
> The real point here is that the JDBC driver is doing something to prompt
> the parser to resolve the types of parameter symbols in particular ways,
> and (I gather) you're doing something different. If you want to match
> the results they get, then you need to supply the same type information
> for parameter symbols to SPI_prepare as they put into Parse messages.
My mistake. I thought that given a statement like:
SELECT p.name FROM people p WHERE p.zipcode = ?
the actual type returned by SPI_getargtype would be inferred by the
expression 'p.zipcode'. I guess that's not the case. Instead I need to
provide the information earlier, like:
SELECT p.name FROM people p WHERE p.zipcode = ?::varchar
is that correct? If so, is there any way that I can automatically infer
the best type?
In response to
pgsql-jdbc by date
|Next:||From: Oliver Jowett||Date: 2006-06-28 00:20:53|
|Subject: Re: [Fwd: Re: [Pljava-dev] char with trailing space, PreparedStatement.setObject|
|Previous:||From: Tom Lane||Date: 2006-06-27 22:31:23|
|Subject: Re: [Fwd: Re: [Pljava-dev] char with trailing space, PreparedStatement.setObject |