Nelson Elhage

Ugh, that's exciting. Thanks for digging into this. I probably don't have time to get things working on 2.x, so it sounds like rolling back is probably the best bet.

(CC @andrewjshults, who has also been thinking about this) I'm definitely open to the idea of supporting unrolling into relational tables. There are a bunch of tricky questions I don't...

I'm not particularly familiar with the capabilities of PostgreSQL's updatable views, off hand. If someone more up to speed on them wants to propose something, I'd be happy to think...

There's some discussion of using MoSQL with redshift in #38. I think the short version is that it's unlikely to work well, unfortunately.

We currently rely on postgres-specific features (notably Postgres' `COPY` for initial bulk import). It probably wouldn't be too hard to refactor to support other backends, but it's not currently on...

The ones I know offhand: - `copy_data` in `lib/mosql/schema.rb`, used for initial bulk import. It should be easy to add a generic importer that uses `INSERT` and is portable (but...

I haven't done so, and I don't know of anyone who has, offhand, but I'd be somewhat surprised if it doesn't work. If you run into any issues, I'd be...

I'd love to see someone play with this! I am not aware of any work in this direction, although we've thrown around the idea (but never implemented anything) at Stripe....

Those log lines are just informative, and not problems -- every `mongod` will have a `local` and `admin` database, and you probably don't want to import them, since they contain...

MoSQL relies on the idempotence of the oplog, and only updates the database once every minute or so. If your application can tolerate a small amount of replay in a...