From: | Fernando Nasser <fnasser(at)redhat(dot)com> |
---|---|
To: | Jason Sando <jsando(at)claritysys(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org, Kim Ho <kho(at)redhat(dot)com> |
Subject: | Re: Allow Byte type in Statement.setObject (v7.3.4) |
Date: | 2003-08-01 13:57:39 |
Message-ID: | 3F2A71D3.1030602@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Have you checked if one of Kim's patches doesn't do that already?
Regards,
Fernando
Jason Sando wrote:
> Would it be troublesome to ask to add:
>
> else if (x instanceof Byte)
> setByte (parameterIndex, ((Byte)x).byteValue ());
>
> into the list of types checked for in AbstractJdbc1Statement.setObject?
>
> I realize Byte is not in the JDBC Spec "setObject conversion table", but you
> already have Short in there and its not in the spec either. I'm working
> with SQL Server, MySQL, and HSql and they all allow Byte.
>
> Now that I think about it, take this as an FYI, and I'll just change my
> program to not call setObject.
>
> Thanks,
>
> - Jason Sando
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
From | Date | Subject | |
---|---|---|---|
Next Message | Renaud Waldura | 2003-08-01 16:57:36 | PostgreSQL & TopLink |
Previous Message | Fernando Nasser | 2003-08-01 13:56:18 | Re: new user rpm content question. |