Linq2CQL3 and pagination support about fluentcassandra HOT 5 OPEN

Currently you set the CQL version in the connection builder to differentiate the type of CQL you want to call.

var conn = new ConnectionBuilder(keyspace: "your keyspace", host: "your host", cqlVersion: FluentCassandra.Connections.CqlVersion.Cql3);
var session = new CassandraSession(conn);
var context = new CassandraContext(session);

var results = context.ExecquteQuery("your cql 3 query here;");

The problem with LINQ is that it is agnostic and there really isn't a good way of differentiating between the two different versions in LINQ. Because in something less than CQL3 you would want that token parameter to have an error thrown, while in CQL 3 you would want it to be included into the CQL query.

It is something I have been wrestling with lately.

from fluentcassandra.

Sorry closed by accident.

from fluentcassandra.

I was looking at your example, and what if the syntax looked like this.

var x = from u in _db.GetColumnFamily("example_table")
           where CqlHelper.Token(u["idx"]) > 10001
           select u;

That way you wouldn't have to implement every token equality sign. You would just need to implement the part that warps the property in token(idx). Do you think that would work better, I haven't had too much time to look at the new spec.

from fluentcassandra.

I belive that the intention of token(x) is to force the user to understand that Cassandra partitionKey is "token-ordered" - that have nothing in common with e.g. natural numbers ordering or string ordering. Therefore I belive that the situation would be better if we can use:
var x = from u in _db.GetColumnFamily("example_table")
where CqlHelper.Token(u["idx"]) > CqlHelper.Token(10001)
select u;

from fluentcassandra.

I see both sides of the comparison need to have token on them. In that case
your original idea might be better.

I am not as familiar with this as you, is there ever a case where token
will only be on one side?

Nick Berardi
(484) 302-0125
Sent on the go from my phone.

On Sep 4, 2012, at 4:46 AM, Pawel Kaplanski [email protected]
wrote:

I belive that the intention of token(x) is to force the user to understand
that Cassandra partitionKey is "token-ordered" - that have nothing in
common with e.g. natural numbers ordering or string ordering. Therefore I
belive that the situation would be better if we can use:
var x = from u in _db.GetColumnFamily("example_table")
where CqlHelper.Token(u["idx"]) > CqlHelper.Token(10001)
select u;

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/58#issuecomment-8256377.

from fluentcassandra.