| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Sylvain Leroux <sl20(at)wanadoo(dot)fr> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Using BigInteger as argument to AbstractJdbc2Statement.setObject |
| Date: | 2009-08-05 11:13:19 |
| Message-ID: | 4A79694F.9060404@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Sylvain Leroux wrote:
> Moreover other scripting languages for the Java platform may exhibit the
> same behavior. So, it would be great if we have support for passing
> BigInteger as argument to the setObject method in prepared statements.
> Even if it's not required by the JDBC API.
>
> Best of all, the patch is trivial as you will see: I send the result of
> a ``cvs diff -u8pN'' as an attachment.
Why NUMERIC instead of an integer type?
Might as well make setBigInteger() private if you're not also going to
expose it on PGStatement (I don't think it needs to be exposed there)
Incidentally, the JDBC spec does provide a standard mapping from
BigDecimal (not BigInteger) to NUMERIC.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sylvain Leroux | 2009-08-05 13:03:33 | Re: Using BigInteger as argument to AbstractJdbc2Statement.setObject |
| Previous Message | Michael Schwipps | 2009-08-05 10:35:47 | float4 or real in function parameter -> PSQLException: ERROR function in_test4(double precision) does not exist |