Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of eevans@acunu.com designates
 209.85.210.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1314521276.99952.YahooMailNeo@web32502.mail.mud.yahoo.com>
References: <1314521276.99952.YahooMailNeo@web32502.mail.mud.yahoo.com>
Date: Sun, 28 Aug 2011 10:35:59 -0500
Message-ID: 
 <CAL35Oi3C4dVaoYdmpE+cqdrcZWiM0a6-fCczHD6eCj1OTrOFyg@mail.gmail.com>
Subject: Re: CqlResult in CassandraConnection
From: Eric Evans <eevans@acunu.com>
To: dev@cassandra.apache.org, Vivek Mishra <vivek.mishra@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 28, 2011 at 3:47 AM, Vivek Mishra <vivek.mishra@yahoo.com> wrot=
e:
> Recently i can see changes made in jdbc connection API.
>
> Wondering why are we returning CqlResult from CassandraConnection, ideall=
y it should return ResultSet as jdbc api.
>
> Any thoughts?

The execute methods aren't a part of the java.sql.Connection
interface, but they are public, and so shouldn't be returning Thrift
structs.  Maybe we just need to drop the public modifier.

Can you open a ticket Vivek?

--=20
Eric Evans
Acunu |=A0http://www.acunu.com=A0| @acunu