tself.
Once I am done with its intial designing I'll share with you guys. If at any
moment i feel that it won't work, will update in that case also.
On Sun, Apr 11, 2010 at 3:58 PM, Mark Robson wrote:
> On 11 April 2010 07:59, Lucifer Dignified wrote:
>
>> For a very simple qu
clear this time. Should you have any queries feel free
to revert.
On Sun, Apr 11, 2010 at 2:01 PM, Benjamin Black wrote:
> Sorry, I don't understand your example.
>
> On Sun, Apr 11, 2010 at 12:54 AM, Lucifer Dignified
> wrote:
> > Benjamin I quite agree to you, but
Dop
You can help us all by sharing your experiences here, so that new users dont
face the same problem :
A group to bring all HA force together (help the effort)
http://www.facebook.com/groups/edit.php?edit_members&gid=116428271708033#!/group.php?gid=116428271708033
On Sat, Apr 10, 2010 at 8:19
Hi
I've been thinking of using cassandra for our existing application, which
has a very complex RDBMS schema as of now, and we need to make a lot of
queries using joins and where.
Whereas we can eliminate joins by using duplicate entries, its still hard to
query cassandra. I have thought of a way
Benjamin I quite agree to you, but what in case of duplicate usernames,
suppose if I am not using unique names as in email id's . If we have
duplicacy in usernames we cannot use it for key, so what should be the
solution. I think keeping incremental numeric id as key and keeping the name
and value
