From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Kevin Wooten <kdubb(at)me(dot)com> |
Cc: | Dave Cramer <davecramer(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL gaps wrt to java, and jdbc |
Date: | 2015-07-07 20:24:43 |
Message-ID: | 559C358B.1000601@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 07/07/2015 11:04 PM, Kevin Wooten wrote:
> As far as “coercion" goes maybe a better term would be “deduction”.
> There are numerous cases where it would be great if we could send the
> server a “don’t care” type and just a binary format. Instead we
> have to specify a type and format together. Doing this causes issues
> in edge cases (e.g. strings coming back padded because we specified
> varchar but the column was text).
Oh, are you talking about query parameters, sent from the client to the
server? The type OID and format code are not actually sent in the same
message - you give the OID in the Parse message and the format code in
Bind. You don't have to specify the OID in the Parse if you don't want
to, and the server will deduce the most sensible one from the query
context. After the Parse, you can find out what the server deduced by
sending a ParameterDescription message, and then form the appropriate
binary representation for the deduced type, and send it with Bind. Am I
missing something?
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2015-07-07 20:26:33 | Re: PostgreSQL gaps wrt to java, and jdbc |
Previous Message | Dave Cramer | 2015-07-07 20:16:29 | Re: PostgreSQL gaps wrt to java, and jdbc |