Re: Caching driver on pgFoundry?
| От | Oliver Jowett |
|---|---|
| Тема | Re: Caching driver on pgFoundry? |
| Дата | |
| Msg-id | 46E31673.4070504@opencloud.com обсуждение исходный текст |
| Ответ на | Re: Caching driver on pgFoundry? (Dave Cramer <pg@fastcrypt.com>) |
| Ответы |
Re: Caching driver on pgFoundry?
|
| Список | pgsql-jdbc |
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? -O
В списке pgsql-jdbc по дате отправления: