___
> From: Rick Shaw
> To: dev@cassandra.apache.org; Vivek Mishra
> Sent: Monday, August 29, 2011 12:59 AM
> Subject: Re: CqlResult in CassandraConnection
>
> The reason they are set up that was is to clearly delineate between methods
> that there are no plans to implemen
roadmap?
Vivek
From: Rick Shaw
To: dev@cassandra.apache.org; Vivek Mishra
Sent: Monday, August 29, 2011 12:59 AM
Subject: Re: CqlResult in CassandraConnection
The reason they are set up that was is to clearly delineate between methods
that there are no plans
t; To: dev@cassandra.apache.org
> Cc: Vivek Mishra
> Sent: Sunday, August 28, 2011 9:39 PM
> Subject: Re: CqlResult in CassandraConnection
>
> The class itself is not public, so it is generally protected from misuse, but
> it is a good recommendation to remove the public modifier
CassandraConnection, ResultSet and
Statement sub class?
Vovel
From: Rick Shaw
To: dev@cassandra.apache.org
Cc: Vivek Mishra
Sent: Sunday, August 28, 2011 9:39 PM
Subject: Re: CqlResult in CassandraConnection
The class itself is not public, so it is generally protected from
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.
