You could store the order as the first part of a composite string say first
picture as A and second as B. To insert one between call it AA. If you
shuffle alot the strings could get really long.
Might be better to store the order in a separate column.
Neither solution mentioned deals with concurr
; As it stands, you would need to iterate over all of the users albums to
>> locate the photo and remove it; that's no good.
>>
>> Probably need another table that holds just the photo / album
>> identifiers, an index. So when the user deletes a photo, you ask the index
tly started learning cassandra but still have troubles
> understanding the best way to design a cassandra database.
> I've posted my question already on stackoverflow but because this would
> very likely result in a discussion, it got closed. Orginal question here:
> http://stackoverflow.
atterns-Page
>
> Later,
> Dean
>
> From: David Mohl mailto:d...@dave.cx>>
> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Friday, December 21,
r 21, 2012 4:49 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Correct way to design a cassandra database
Hello!
I've recently started learning cassandra but still have troubles understanding
the best way
