| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
| Cc: | Radosław Smogura <rsmogura(at)softperience(dot)eu>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [JDBC] JDBC and Binary protocol error, for some statements |
| Date: | 2010-11-25 19:42:09 |
| Message-ID: | 18034.1290714129@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Maciek Sakrejda <msakrejda(at)truviso(dot)com> writes:
>> But to the last part of cited protocol specification, when I've sent message with statement parameter's type int4, int8, varchar the format
>> field wasn't set to 0, but 1.
> I wasn't able to reproduce that with my standalone test case. When I
> changed the parameter oid to 23, I still got the same behavior. Can
> you alter my test case to reproduce the error?
I'd be really surprised if that affected the server-side behavior.
OTOH, it seems possible that the JDBC driver might behave differently
depending on whether parameter types were prespecified or not --- it
might issue Describe earlier in order to get the parameter types,
perhaps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2010-11-25 20:21:39 | Re: [JDBC] JDBC and Binary protocol error, for some statements |
| Previous Message | Radosław Smogura | 2010-11-25 19:34:41 | Re: [JDBC] JDBC and Binary protocol error, for some statements |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2010-11-25 20:21:39 | Re: [JDBC] JDBC and Binary protocol error, for some statements |
| Previous Message | Radosław Smogura | 2010-11-25 19:34:41 | Re: [JDBC] JDBC and Binary protocol error, for some statements |