Yes, but it relies on extra jars who's pedigree we don't control. Which is part of the security issue.
As I said earlier I like this idea as a high performant minimal functioning driver. By minimal functioning I'd probably not implement all of the metadata API(s)
On Tue, Mar 12, 2013 at 2:55 PM, Kevin Wooten <kdubb@me.com> wrote:
Just to put this to bed, with regards to the project under discussion, the final delivery will be a single jar file with no external dependencies. Just haven't gotten that far yet.
>>> I think using 3rd party dependencies is the proper way to go forward >>> instead of reimplementing all required functionalities in every JDBC driver. >>> That is not to say that the required dependencies should be kept to minimum. >> >> Two cents: it troubles me always when I hear this reasoning because the >> external dependencies still increase the maintenance costs, no matter how >> well managed. For instance, for JDBC/DB stuff, many people care (or are >> mandated to care) about security and the associated maintenance. > > I could not agree more. > > > -- > Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc
