From: | "Markus KARG" <markus(at)headcrashing(dot)eu> |
---|---|
To: | "'List'" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Adding new dependencies for in-core |
Date: | 2015-06-30 20:22:09 |
Message-ID: | 014501d0b372$7118f8d0$534aea70$@eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I won't say it is over-engineering: I think it is always a good idea to *explicitly* pick a strategy instead of taking one *for granted* just because it comes with the box. For example, at the JCP we discuss the intensive use of the Java Cache API for various endavious exactly like this one. :-)
-----Original Message-----
From: Vladimir Sitnikov [mailto:sitnikov(dot)vladimir(at)gmail(dot)com]
Sent: Dienstag, 30. Juni 2015 20:14
To: Steven Schlansker; Markus KARG
Cc: List
Subject: Re: [JDBC] Adding new dependencies for in-core
>I'm having trouble believing any end user will replace the caching strategy for prepared statements.
My wild guess is Markus a bit over-engineers _internal_ implementation of the driver.
I think he hints best practices of coding so the driver does not get tied to the single cache implementation.
Markus, did I get you right?
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Markus KARG | 2015-06-30 20:25:18 | Re: SQLJSON |
Previous Message | Markus KARG | 2015-06-30 20:18:37 | Re: Adding new dependencies for in-core |