On 6/24/2013 4:18 PM, Kevin Wooten wrote:
> Second, porting my implementation back to Java 5/6 and/or PostgreSQL
> servers prior to 9.2. The current driver has lots of special case
> code for servers and now JDK’s that have been EOL’d. My project
> implementation currently has none, it runs on JDK 7/JDBC 4.1 and
> Postgres >= 9.2. I believe there is a more elegant way to handle
> these cases going forward than the option used in the mainstream
> project of abstract/concrete classes for each JDBC version. I think
> JDBC differences should be handled with the maven pre-processor plugin
> to conditionally compile for each JDBC. Server differences can still
> use special case code and/or polymorphic classes to address the
> problem/feature at hand.
speaking as a user and system administrator, I would NOT want to need to
use different JAR files for each {jvm,postgres} version. that would be a
nightmare.
we have a LOT of systems in our manufacturing operations that are
running older versions of {os, postgres, jvm} for various reasons, not
the least of which is upgrades often break things in very non-obvious ways.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
