ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: jdbc vs jdbc2 packages
Date Tue, 07 Feb 2017 00:44:15 GMT
There are two implementations of JDBC driver - based on legacy thin client
(jdbc package) and on client node (jdbc2). The first one was deprecated
when we introduced the latter, but now I tend to think that this was not a
right decision. Thin client driver provides worse performance, but it's
much easier to use, never requires additional dependencies like Spring and
can be used from any remote machine. Probably we can consider undeprecating


On Mon, Feb 6, 2017 at 2:02 AM, Sergi Vladykin <sergi.vladykin@gmail.com>

> Guys,
> We have 2 different packages: jdbc and jdbc2. Everything in jdbc is
> deprecated. Because of that new features like DML support were not added
> there.
> This seems to cause some problems to our users. Can someone clarify, did we
> deprecated these classes wrongly and we have to continue developing them or
> what?
> Sergi

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message