“delete cascade” seems like a good way to think about it too. The same lifetime and ownership considerations exist in sql when deciding to cascade or not

Honestly if you never isComponent nothing will break. You will have to pull those refs explicitly when you want them, and deletion will orphan entities instead of retracting them

Is there any difference under the hood if I use (mapv (partial pull db pattern) eids) instead of (pull-many db pattern eids) ?

I’m having issues restoring an older backup to my local dynamodb storage and I’m wondering if anyone can help? the following error is produced by dynamodb in the console: https://pastebin.com/8avZbXD7

I originally backed up my datomic free some time ago, and now I actually need this data again and am trying to get it restored

urgh, looks like ddb-local is completely broken now, will nuke away and restore independent backups and see how it goes

oh snap, ok, so it seems my problem was starting ddb with the -optimizeDbBeforeStartup flag… it must have corrupted something, somehow

debugging a “not on my box” issue. i’ve packaged an uberjar that runs its own peer, and I’ve included the sql driver in that jar, however when my colleague tries to run it they get java.sql.SQLException: No suitable driver. jar -tf shows the expected driver names on the classpath. any other obvious things I should check?

connection string?

we’re using the same connection string. mine works there’s does not