News for hackers. Stuff that matters.

A comment on Migration from Postgres to Datomic. Parent comment

Re:Migration from Postgres to Datomic by jarym on Thursday July 06, 2017 @10:03PM (#14715495)
Conceptually that is fine but there are complications (speaking based on recent and ongoing experience on a project I'm working on):

1. When you have multiple entity tables that are inter-related, snapshotting one in isolation is not sufficient.

2. When only certain changes on certain fields should result in a new snapshot.

Granted, both of these are solvable with built-in Postgres mechanisms (and a bit of co-operation from the application server) but simple it is not.

In our case we also move historic records to a second 'history' table.

[ Parent | on HN ]
Re:Migration from Postgres to Datomic by ComodoHacker on Friday July 07, 2017 @01:40AM (#14716338)
To add to your list, with 1. referential integrity becomes a problem. Basically you move it up the stack into the application code and lose consistency guarantees RDBMS can provide.

I'm curious wether Datomic supports RE and how.

[ Parent | on HN ]