I'm working on a legacy cljs application using datascript, and it uses strings for :db/ids. I want to upgrade datascript, but it seems I'm no longer allowed to use strings as eids - is there a good way of doing this? It would be infeasible to manually change all IDs in the code from strings to numbers.

@conan: there’s no easy way

i was afraid you'd say that!

You have to migrate to external ids, where string id is just an attribute with {:db/unique :db.unique/identity}

you can keep referencing your entities using lookup syntax

say you’d name your attr :external-id

then you can use [:external-id <string>] almost everywhere entity id is expected

and add to schema { :external-id {:db/unique :db.unique/identity} }

yeah, i see. :db/id really is just an internal database id, not meant for cramming stuff into (as we did, we put uuids in there)

thanks though, it saves me a lot of time to know that!

yep, it was fun to being able to store anything in ids

but performance really suffer

now, if you really need it, you walk an extra mile, but by default you don’t pay that price

@tonsky: question about rum: would there be any issues using something like re-com UI components with the reactive mixin?