| From: | Barry Lind <blind(at)xythos(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: CVS JDBC driver will try to use server-side-prepare on |
| Date: | 2003-08-21 01:31:51 |
| Message-ID: | 3F442107.3080908@xythos.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver Jowett wrote:
> On Fri, Aug 15, 2003 at 09:55:02AM -0700, Barry Lind wrote:
>
>
>>But in short the reason is, that in general using the current
>>prepared implementation will be *slower* than not using it, unless you
>>are reusing the statement a number of times. [...]
>
>
> Hmm, has anyone considered an approach where the statement begins to use
> server-side prepare after it has been used N times? (the assumption being
> that it will continue to be reused). N=2 is probably enough to get 90% of
> the cases :)
>
I agree that this would likely work quite well. If you use it more than
once you are likely to use it again.
--Barry
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2003-08-21 01:46:54 | Re: CVS JDBC driver will try to use server-side-prepare on |
| Previous Message | Richard DeGrande | 2003-08-20 22:16:16 | patch: add a finalizer to AbstractJdbc1Statement |