On Tue, 15 Nov 2011, Teun Hoogendoorn wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6293
> PostgreSQL version: 9.1
> Description:JDBC driver performance
> Details:
>
> Using the postgresql-9.1-901.jdbc3.jar driver instead of
> postgresql-9.0-801.jdbc3.j
of your if statement. If the
valor variable is a String, the JDBC driver is assigning it a string
type. You may want to do setObject(1, valor, Types.INTEGER) or
convert it prior to doing the setObject call to an appropriate
numeric type.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-
ypes.OTHER) to indicate that you don't know
that the Java type you are passing is correct.
3) Use the stringtype=unspecified URL parameter to indicate that all
String bindings may not really be strings.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
esultSet and call getString() on a UUID field, it will
certainly work. Mapping the UUID to BLOB or CLOB is incorrect. I'm not
sure why your attempt to map it to a String didn't work, but you are
not convincing Hibernate to use a plain getString call.
Kris Jurka
--
Sent via pgsql-bu
return a UUID object.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
cuteBatch%28%29
>
> It seems better to report no number at all rather than a number (INT_MAX) that
> is known to be wrong.
What about Statement.executeUpdate? It has provision for returing a
batch execution response code.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@po
> INT_MAX while still
throwing an exception if we get something that is truly undecipherable?
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
201 - 207 of 207 matches
Mail list logo
