Fork me on GitHub
#datomic
<
2016-07-12
>
stijn07:07:36

@zentrope, @marshall I ran into the same issue with aleph and latest datomic. current solution for me: going back to datomic 0.9.5372

pheuter15:07:00

Is there any potential harm in transacting the same schema attributes multiple times?

pheuter15:07:21

for example, when doing naive migrations of new attributes, not worrying about filtering out attributes already in the db

marshall15:07:23

@pheuter: If a given transaction has no ‘novel’ datoms, it will create an empty transaction entity in the log. Otherwise, no, re-asserted datoms are ignored

marshall15:07:02

In general I wouldn’t do it all the time (i.e. on startup), but occasionally (as in part of a migration) shouldn’t be a big deal

dominicm15:07:20

@pheuter: You've probably seen this, but just in case https://github.com/rkneufeld/conformity

pheuter15:07:09

this is great, thanks guys! yeah, this isn’t an on-startup thing as much as one-off migrations of schema changes

davin15:07:13

conformity seems to be heavily inspired by the day-of-datomic code for migrations, that is worth checking out as well: https://github.com/Datomic/day-of-datomic/blob/master/src/datomic/samples/schema.clj

pheuter17:07:30

yeah i saw that earlier, just wasn’t sure if that was required