| From: | "Neil Murray" <nhm(at)mimecast(dot)net> |
|---|---|
| To: | "pgsql-jdbc (at) postgresql (dot) org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: jdbc pooling question |
| Date: | 2004-01-12 10:10:49 |
| Message-ID: | 024601c3d8f4$5f0b45e0$020ba8c0@NOTEBOOK2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> Plus there are a number of robust open-source connection pool
> implementations available. I use Apache dbcp (via Tomcat) and it all works
> very nicely and can also clean up resource leaks left by non-programmers
> who don't know how to correctly use a finally block :)
>
> OT, I can't really see the point of re-inventing the wheel by providing
> our own connection pooling. Does anyone else have any views on this?
I should have known that Apache would have had one (but I didn't). I forgot
the cardinal rule ... when in doubt, visit Apache Jakarta.
Many Thanks
Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2004-01-12 12:54:15 | Re: PreparedStatement parameters and mutable objects |
| Previous Message | Keith C. Klopfer | 2004-01-12 08:32:24 | Weird ILIKE behavior: Solved |