Bothering at my usual cadence 😅: currently I'm working off of the master-branch (with its many lovely fixes/additions)- but at the moment when I try to build my clojure project, I get an error as datalevin.migrate/ensure-jar is trying to download a non-existent datalevin-1.0.0-standalone release (as far as I know, I shouldn't have anything that needs migrating, but I suppose that compilation requires it to be present anyhow).
Should I drop back to 0.10.18 in the meantime, until the big 1.0 lands? I tried editing the prepped gitlib, setting datalevin.constants/require-migration? to false, but it didn't seem to have any bearing on the whether ensure-jar evaluates
this is a bug on version handling. Fixed in master.
Is there a way to add aliases for attributes in datalevin? that's one of the recommended ways to evolve the schema by datomic
Honestly I'm just curious in general about the tack most people take to evolving a datalevin db in a live system over time
Like do you have a system of migrations that does calls to update-schema through a whole series of updates after pinning an initial version of the base schema map, or do you have only accreting changes to that schema map, etc.
Right now, one can rename an attribute. Adding aliases to attribute could be a future feature if people feel it is useful.