Re: Caching driver on pgFoundry?
От | Dave Cramer |
---|---|
Тема | Re: Caching driver on pgFoundry? |
Дата | |
Msg-id | 844D9561-315B-4A90-93AA-F2940BB3C374@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Caching driver on pgFoundry? (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: Caching driver on pgFoundry?
Re: Caching driver on pgFoundry? |
Список | pgsql-jdbc |
On 8-Sep-07, at 5:38 PM, Oliver Jowett wrote: > Dave Cramer wrote: >> On 7-Sep-07, at 9:13 AM, Oliver Jowett wrote: >>> >>> What is the implementation advantage of making statement pooling >>> part of the main driver? There are maintenance issues which count >>> *against* it being part of the driver so you need to provide a >>> good reason to include it. >>> >> Well, it has to be maintained regardless of where it is. So how >> does that make any difference ? > > Err if it is part of the main driver it needs to be maintained as > part of the main driver and will follow the main driver's release > cycle. Others have commented on the same thing. It also increases > the complexity of the main driver, making it harder for a > particular person to maintain the whole thing. > > I'm going to ask again: What is the implementation advantage of > making statement pooling part of the main driver? > It's simpler, there's about half a dozen classes and one if statement as opposed to implementing the Connection and Statement interfaces for 3 versions of jdbc and yet another build system that does the same. Dave > -O
В списке pgsql-jdbc по дате отправления: