| From: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(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:59:36 |
| Message-ID: | 1151096376.21238.93.camel@archimedes |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 2006-06-23 at 15:46 -0500, Kris Jurka 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.
Ah, yes that's where I was confused. Now I understand why it was such a
pain to support things like timestamp with/without timezone; you don't
get the describe statement back until you've already run the BIND.
-- Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christiano Tavares | 2006-06-23 22:35:42 | Dúvida |
| Previous Message | Kris Jurka | 2006-06-23 20:46:33 | Re: Binary tx format for an array? |