On Wed, Jan 22, 2014 at 06:44:20PM +0100, Kasper Middelboe Petersen wrote:
I'm a little worried about the data model I have come up with for handling
highscores.
I have a lot of users. Each user has a number of friends. I need a
highscore list pr friend list.
I would like to
On Tue, Jan 21, 2014 at 10:40:39AM -0800, Drew Kutcharian wrote:
Thanks, I was actually thinking of doing that. Something along the lines
of
CREATE TABLE user (
idtimeuuid PRIMARY KEY,
emailtext,
nametext,
...
);
CREATE TABLE user_email_index
On Wed, Jul 31, 2013 at 03:10:54PM -0700, Jonathan Haddad wrote:
It's advised you do not use compact storage, as it's primarily for
backwards compatibility.
Yes indeed, I understand what it does and why now, but only because
I was pointed to the thrift-to-cql document. The CQL
I thought that part of the point of Cassandra was that, unlike a
standard relational database, each row does not have to have the same
set of columns. I don't understand how this squares with CQL. If I want
to have a table (column family?) with a few fixed columns that are
relevant to every row, I
On Wed, Jul 31, 2013 at 02:21:52PM +0200, Alain RODRIGUEZ wrote:
I like to point to this article from Sylvain, which is really well
written.
http://www.datastax.com/dev/blog/thrift-to-cql3
Ah, thankyou, it looks like a combination of multi-column PRIMARY KEY
and use of collections may
