Thanks Rick.
As to class level hierarchy, I am not sure I understand the reference? Could
you elaborate?
As we have got 1 super class and sub class in place for (
AbstractCassandraConnection,AbstractResultSet and AbstractStatement). So
thought to ask for if any other implementation is on roa
The reason they are set up that was is to clearly delineate between methods
that there are no plans to implement any time in the near future; it minimizes
the distraction in the classes that get a lot of activity. It is not necessary,
but it was done that way when I started looking at the code a
I was looking at AbstractCassandraConnection,AbstractResultSet and
AbstractStatement classes. Name looks to me quite confusing as none of them is
an abstract class. 1 more thin, any specific reason for creating class level
hierarchy?
Plans for any other implementation/s of CassandraConnectio
The class itself is not public, so it is generally protected from misuse, but
it is a good recommendation to remove the public modifier on those
non-interface imethods as well. I'll see to it.
On Aug 28, 2011, at 11:35 AM, Eric Evans wrote:
> On Sun, Aug 28, 2011 at 3:47 AM, Vivek Mishra wrote
On Sun, Aug 28, 2011 at 3:47 AM, Vivek Mishra wrote:
> Recently i can see changes made in jdbc connection API.
>
> Wondering why are we returning CqlResult from CassandraConnection, ideally it
> should return ResultSet as jdbc api.
>
> Any thoughts?
The execute methods aren't a part of the java.
Hi,
Recently i can see changes made in jdbc connection API.
Wondering why are we returning CqlResult from CassandraConnection, ideally it
should return ResultSet as jdbc api.
Any thoughts?
-Vivek
