Also: there is nothing stopping your app from pooling connections on a
per-keyspace basis. If I were writing an app where I were trying to
partition on keyspace per customer, then that is what I would do.
On Sun, Jun 6, 2010 at 9:27 PM, Jonathan Ellis wrote:
> The common case is that you will ha
The common case is that you will have app-per-keyspace, so switching
keyspace on an active conn is an unusual thing to do.
Optimizing the common case at the expense of the rare one is normal,
although it does sting when you're working on one of the rare ones.
On Sun, Jun 6, 2010 at 9:10 PM, Benja
Can someone enlighten me as to the purpose of set_keyspace() and the
elimination of the keyspace args from calls? I understand there was a
discussion of the issue before I joined the list several months ago.
For those with several keyspaces, or many keyspaces, as when using a
keyspace per customer
