From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Pre-processing during build |
Date: | 2015-06-18 20:10:19 |
Message-ID: | CADK3HHLyQ4xD43J_+M2A5HXN_vpe3xHzwZnkDApmy1Rvrk+xow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On 18 June 2015 at 16:08, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 6/18/2015 12:33 PM, Vladimir Sitnikov wrote:
>
>> John> and that stuff NEVER gets updated until the equipment is replaced.
>>
>> That is cool. However, that means you don't care if pgjdbc drops
>> updates for JDK6, do you?
>>
>
> as long as a legacy version remains available, sure, I dunno why not.
> the older stuff is /very/ stable anyways, most of the work is towards
> supporting new features of the new versions, is it not?
Somewhat .. there is also work being done to support new features of
Postgres, for instance json, and bidirectional copy (not implemented but
new in pg)
>
>
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Markus KARG | 2015-06-18 20:11:07 | Re: Pre-processing during build |
Previous Message | Dave Cramer | 2015-06-18 20:09:03 | Re: Pre-processing during build |