; then CouchDB is not for you."
>>
>> I think that's a little overstated. Instead, realize that updates to a
>> document are atomic, and therefore you should model your transactions
>> as documents.
>
> Sure, that is exactly the point of the banking recipe, and
rstated. Instead, realize that updates to a
> document are atomic, and therefore you should model your transactions
> as documents.
Sure, that is exactly the point of the banking recipe, and I believe
Andy -- the original poster -- got it, but he felt it the model was
unsuitable to the kinds of tr
AM, Andy wrote:
> >>
> >> Im well versed in Java/Hibernate/RDBMS. Im trying to get my head around
> how NoSQL does not use transactions.
> >> I read the Banking Recipe which didn't really do the job:
> http://guide.couchdb.org/draft/recipes.html
> >> So i
ou should model your transactions
as documents.
B.
On Sun, Nov 14, 2010 at 10:53 PM, Luciano Ramalho wrote:
> On Sun, Nov 14, 2010 at 5:39 AM, Andy wrote:
>>
>> Im well versed in Java/Hibernate/RDBMS. Im trying to get my head around how
>> NoSQL does not use transactions
On Sun, Nov 14, 2010 at 5:39 AM, Andy wrote:
>
> Im well versed in Java/Hibernate/RDBMS. Im trying to get my head around how
> NoSQL does not use transactions.
> I read the Banking Recipe which didn't really do the job:
> http://guide.couchdb.org/draft/recipes.html
> So
n Java/Hibernate/RDBMS. Im trying to get my head around how
> NoSQL does not use transactions.
> I read the Banking Recipe which didn't really do the job:
> http://guide.couchdb.org/draft/recipes.html
> So if I wanted to write an online banking app, I would have say a million
>
Im well versed in Java/Hibernate/RDBMS. Im trying to get my head around how
NoSQL does not use transactions.
I read the Banking Recipe which didn't really do the job:
http://guide.couchdb.org/draft/recipes.html
So if I wanted to write an online banking app, I would have say a mi
