Dave Cramer <Dave@micro-automation.net> writes:
> By de-coupling the driver and letting it evolve on it's own time table
> we are free to apply patches whenever they are available.
That point of view would be more easily maintained if you separated out
the JDBC driver as its own project (see gborg). As long as JDBC is part
of the server CVS tree and is shipped in server releases, you really
cannot ignore the server release cycle. Or at least, you do so at
peril of alienating users who expect to find a reasonably-maintained
JDBC driver in their downloads. If they have to download JDBC
separately to get important bug fixes, aren't you wasting their time
and bandwidth by including an old JDBC in the server distribution?
regards, tom lane