If you want to use Cassandra, you should probably store each
historical value as a new column in the row.
On Wed, Apr 14, 2010 at 12:34 AM, Yésica Rey wrote:
> I am new to using cassandra. In the documentation I have read, understand,
> that as in other non-documentary databases, to update the va
Here here on documentation.
For example thrift examples in python and java. That is great but I've
never coded in either (and am limited to perl or C at work because when
have 5 years worth of code and experience with other modules provided
for those languages). So I'm stuck with whatever the
The closest is http://github.com/driftx/chiton
On Wed, Apr 14, 2010 at 2:57 AM, Yésica Rey wrote:
> Ok, thank you very much for your reply.
> I have another question may seem stupid ... Cassandra has a graphical
> console, such as mysql for SQL databases?
>
> Regards!
>
On Wed, Apr 14, 2010 at 5:13 PM, Zhiguo Zhang wrote:
> I think it is still to young, and have to wait or write your self the
> "graphical console", at least, I don't find any until now.
Frankly speaking, I'm OK to be without GUI...But I am really
disappointed by those so-called 'documents'.
I rea
I think it is still to young, and have to wait or write your self the
"graphical console", at least, I don't find any until now.
On Wed, Apr 14, 2010 at 10:04 AM, Bertil Chapuis wrote:
> I'm also new to cassandra and about the same question I asked me if using
> super columns with one key per ve
I'm also new to cassandra and about the same question I asked me if using
super columns with one key per version was feasible. Is there limitations to
this use case (or better practices)?
Thank you and best regards,
Bertil Chapuis
On 14 April 2010 09:45, Sylvain Lebresne wrote:
> > I am new to
Ok, thank you very much for your reply.
I have another question may seem stupid ... Cassandra has a graphical
console, such as mysql for SQL databases?
Regards!
> I am new to using cassandra. In the documentation I have read, understand,
> that as in other non-documentary databases, to update the value of a
> key-value tuple, this new value is stored with a timestamp different but
> without entirely losing the old value.
> I wonder, as I can restore the hi
Values with newer timestamps completely replace the old values. There
is no way to access historic values.
On Wed, Apr 14, 2010 at 12:34 AM, Yésica Rey wrote:
> I am new to using cassandra. In the documentation I have read, understand,
> that as in other non-documentary databases, to update the
I am new to using cassandra. In the documentation I have read,
understand, that as in other non-documentary databases, to update the
value of a key-value tuple, this new value is stored with a timestamp
different but without entirely losing the old value.
I wonder, as I can restore the historic
10 matches
Mail list logo
