I think you need to decouple the database from the replication. Replication
management is not a first-class citizen in CouchDB (yet?) and the problems you
present show that.
Basically what you're looking at is a message board service, where clients post
requests ("send this email") and servers
On 12 November 2010 00:27, Andrei Varanovich wrote:
> Do you mean in the http://127.0.0.1:5984/_utils/config.html ?
> The thing is that I cannot get access to it as soon as I am not logged in.
you can edit the local.ini file directly from notepad or your editor
of choice, then restart couch from
Hi Nolan,
I haven used the rewrite option in couchdb yet but you may want to
check the couchdb log to see if the rewrite is working as you expect
it. Sorry I cannot be more helpful.
Regards,
On Wed, Nov 10, 2010 at 11:32 PM, Nolan Darilek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SH
node.js + CouchDB == Crazy Delicious by Mikeal Rogers
http://jsconf.eu/2010/speaker/nodejs_couchdb_crazy_delicious.html
I was watching this a couple days ago and I've been thinking about how
to deal with instance and service (think of sending emails as a
"service") failures. Because it's easy to
On Sun, Nov 14, 2010 at 3:42 PM, Luciano Ramalho wrote:
> On Sun, Nov 14, 2010 at 9:14 PM, Robert Newson
> wrote:
>> "If you really need transactions in the classical, RDBMS sense, where
>> you need to update a bunch of related records in one atomic operation,
>> then CouchDB is not for you."
>>
On Sun, Nov 14, 2010 at 9:14 PM, Robert Newson wrote:
> "If you really need transactions in the classical, RDBMS sense, where
> you need to update a bunch of related records in one atomic operation,
> then CouchDB is not for you."
>
> I think that's a little overstated. Instead, realize that updat
On Mon, Nov 15, 2010 at 10:14 AM, Robert Newson wrote:
> "If you really need transactions in the classical, RDBMS sense, where
> you need to update a bunch of related records in one atomic operation,
> then CouchDB is not for you."
>
> I think that's a little overstated. Instead, realize that upda
"If you really need transactions in the classical, RDBMS sense, where
you need to update a bunch of related records in one atomic operation,
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
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 if I wanted to write an
I'm personally not sure wether the banking example is good one or not, but:
summing up transactions isn't that bad, since the result is saved in the views
b-tree. after first computation you get the result very fast.
On 14.11.2010, at 08:39, Andy wrote:
>
> Im well versed in Java/Hibernate/RDB
10 matches
Mail list logo
