Re: JDBC 4 Compliance

When this somewhat settles out. I'm still open to helping with the web page.
Provied that I can help to contribute in that way with providing a more effect
means to communication todo list, patches/tracking, gap analysis, etc.

Without a means for people to easily understand specific areas to contribute
with direction, and perhaps individual(s) to contact for each area I think the
project is going to continue to be lacking in direction and momentum.

danap.
Dana M. Proctor
MyJSQLView Project Manager

Dave Cramer wrote:
> Tom,
>
> The test suite is not bad, but it certainly could use more tests. I
> doubt it confirms everything.
>
> Plus there are some things you can only test in production
>
>
> On a more general note. After today I will be away from my computer for
> the next 3 days.
> I am going to contemplate my involvement, which at this time is leaning
> towards staying on and developing a team to which I will feel
> comfortable leaving the driver to.
>
> There's been considerable talk about not supporting 4.1, blobs, etc. I'd
> like to understand what is missing; I've asked this before does anyone
> have a gap analysis ?
>
>
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Thu, Jun 27, 2013 at 11:43 PM, Tom Dunstan <pgsql@tomd.cc
> <mailto:pgsql@tomd.cc>> wrote:
>
>     On 27 June 2013 23:50, Mike Fowler <mike@mlfowler.com
>     <mailto:mike@mlfowler.com>> wrote:
>
>         The recurring plan that seems to be developing is to maintain
>         the current driver focusing on it's stability and compatibility.
>         Going forward the energy and focus would be towards a new driver
>         which is liberated from the concerns of backwards compatibility.
>
>
>     Uh, what? Which backwards compatibility were you intending to throw
>     away? Just older JRE versions?
>
>         Long term we'll have to see whether we want to maintain two
>         codebases. For now let's experiment and see how things progress.
>         There are pros and cons to both codebases, neither are perfect.
>         With that in mind this is open source and people are free to do
>         their own thing but there is strength in numbers. We obviously
>         all care about PostgreSQL and it's JDBC driver so let us all try
>         and make the best JDBC driver(s) possible!
>
>
>     As a long-time user of the driver, I'd like to de-lurk to point out
>     that the nervousness about stability which has surfaced in this
>     thread (and which I share) can often point to opportunities to
>     improve automated test coverage.
>
>     Dave, how complete would you say that the existing test suites are?
>     If a new implementation can pass the tests, how much does that say
>     about the driver's completeness or backwards compatibility?
>
>     And for those who have forked the driver or started from scratch, do
>     you have comments on the existing test suite? Or have you written
>     your own?
>
>     If the AIO etc driver is to be developed in parallel with the
>     existing one, it might be an interesting idea to split the tests out
>     into a separate project so that the tests can be run against both
>     drivers. Then improvements in the test suite are shared as well!
>
>     Cheers
>
>     Tom