My understanding from reading the jdbc-spec mailing list is that the
api is work in progress until they are happy with it.
Last updates to the specification was published 2018-10-22 and wasn't
very large, and there has also been debate on if the fundamental
return object should be an Future or if it should be a reactive
stream.
I think there will be more breaking api changes to come, so it's
important to communicate this to those that are interested in
experimenting with the library.
//Alex
Den tis 30 okt. 2018 kl 02:13 skrev Chad Retz <chad.retz@gmail.com>:
>
> Are there any updates on the ADBA abstraction itself? Specifically
> around stability, test suites, potential inclusion in JRE in some
> version, active contribution from anyone on the OpenJDK team, etc.
>
> Thanks,
> Chad
> On Sun, Oct 28, 2018 at 9:38 AM Alexander Kjäll
> <alexander.kjall@gmail.com> wrote:
> >
> > Hi
> >
> > I'm not totally sure if this is the best place for this topic, but as
> > the library was briefly discussed on the list before I'll continue
> > that tradition.
> >
> > There is still a lot more work to be done on the adba driver for
> > postgresql, and the adba specification from oracle is still subject to
> > change.
> >
> > But the driver have also come a long way and is in a state where it
> > would be useful to be able to experiment with it in external projects,
> > and therefore I'm feeling that it's time for a first alpha release.
> >
> > I have a number of questions regading naming and procedure and stuff like that.
> >
> > 1) I feel that the name pgsql2 isn't optimal, maybe change it to pgAdba.
> >
> > 2) Do you want to publish the artifact under the org.postgresql
> > groupId to maven central?
> >
> > 3) Any opinion on version numbering? I was thinking that 0.1.0-ALPHA
> > could be appropriate.
> >
> > //Alex
> >