I'd rather not do it via batch because I'd like the system to be interactive (via a browser). And depending on all this processing to occur outside this subsystem seems less robust. And to touch on your point, this is a pretty big database and exporting like that would make some unhappy dbas. I'm not sure these are good reasons, but at least they are the ones I've thought of.
But ultimately what I've taken from this conversation is that the _changes feed is basically the only way I can build the system I'd like. Unless there is some other way that makes sense. thanks Mike On Mon, Feb 7, 2011 at 11:29 AM, Dirkjan Ochtman <[email protected]> wrote: > On Mon, Feb 7, 2011 at 18:14, Michael Kohout <[email protected]> wrote: > > What does the couch community think of this? Is there some other pattern > > that might result in a simpler system? > > Simple system: use SQL JOINs to fetch all the data for each document > you want in CouchDB, then batch-load those into CouchDB (per few k > documents) as the rows come in from the RDBMS. > > I'm not sure why you'd want to do it some other way? This is the way > I've done it a few times, though admittedly on smaller databases. I > don't think your idea for doing joins in a view is particularly > feasible, though there are things you can do here. > > Cheers, > > Dirkjan >
