Re: RFC Changing the version number for JDBC please ignore

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: RFC Changing the version number for JDBC please ignore
Date: 2016-11-27 14:29:52
Message-ID: CADK3HHJ90DzixQzehDSc-_8ADpNAzAP_dKRPRo2p8b3HdDa6Eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

please ignore this. I fat fingered the email address.

Dave Cramer

On 27 November 2016 at 09:12, Dave Cramer <davecramer(at)gmail(dot)com> wrote:

> We are proposing changing the JDBC version from
> 9.4.xxxx to 42.x.x
>
> We have two issues we are trying to address here.
>
> 1) we do not want to be tied to the server release schedule. This has been
> somewhat addressed already but has left us with the second issue.
>
> 2) Avoid confusion as to which version to use with which server version.
> Currently the naming scheme has 9.4 in it which leads people to believe it
> is for server version 9.4
>
> The driver is version agnostic for the most point so there is no reason to
> tie it to a specific server version.
>
> I've already talked to the package managers and they see no problems.
>
> Please speak up now if you foresee any issues with this idea.
>
> FYI, 42 was more or less chosen at random. But it is large enough to avoid
> any future conflicts with the server, and greater than 9 to avoid issues
> with maven requesting things like > 9
>
>
> Dave Cramer
>

Browse pgadmin-hackers by date

  From Date Subject
Next Message Surinder Kumar 2016-11-28 15:46:52 Re: Re: [pgAdmin4][Patch]: Fixes #1986 - Properly handle non-ascii characters while loading & saving file
Previous Message Magnus Hagander 2016-11-27 14:15:25 Re: RFC Changing the version number for JDBC