[
https://issues.apache.org/jira/browse/CASSANDRA-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096525#comment-13096525
]
Eric Evans commented on CASSANDRA-3130:
---------------------------------------
I was going to cite Postgres's docs (i.e. "Any given client connection to the
server can access only the data in a single database, the one specified in the
connection request."), but then realized that with schemas
(http://www.postgresql.org/docs/9.0/static/ddl-schemas.html), the same
capability is there.
So, I stand corrected.
> CQL queries should alow talbe names to be qualified by keyspace
> ---------------------------------------------------------------
>
> Key: CASSANDRA-3130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3130
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Priority: Minor
> Fix For: 1.1
>
>
> While the 0.6.X api was "ugly" in terms of method signatures, it did allow
> you to use the same client to query multiple keyspaces without having to call
> set_keyspace(String). I totally dislike set_keyspace but I know the thrift
> API is definitely not changing.
> The following command sequence is three RPC operations.
> {noformat}
> select * from cf;
> use otherkeyspace;
> select * from othercf;
> {noformat}
> CQL should allow us to do:
> {noformat}
> select * from keyspace1.cf;
> select * from keyspace2.cf;
> {noformat}
> This will make the connection pool management on the client much easier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
