| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Michael Guyver <kenevel(at)googlemail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Binary tx format for an array? |
| Date: | 2006-06-23 20:46:33 |
| Message-ID: | Pine.BSO.4.63.0606231543240.247@leary2.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 23 Jun 2006, Mark Lewis wrote:
> As far as I can tell from reading the JDBC CVS code, the sequence for
> preparing and executing a statement for the first time is:
>
> PREPARE (name=my_statement)
> DESCRIBE STATEMENT (name=my_statement)
> SYNC/FLUSH
> Read Responses
>
> BIND (portal=my_portal)
> DESCRIBE PORTAL (name=my_portal)
> EXECUTE (portal=my_portal)
> SYNC/FLUSH
> Read Responses
>
Nope. There is no Sync in the middle there. The driver sends Parse,
Describe Statement, Bind, Execute, Sync all at once. You may be confused
by the driver's ability to Parse/Describe/Sync a query to implement
ParameterMetaData, but that's an unusual operation, not the normal path.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Lewis | 2006-06-23 20:59:36 | Re: Binary tx format for an array? |
| Previous Message | Dave Cramer | 2006-06-23 20:40:16 | Re: Binary tx format for an array? |