Dave Dixon

+1. Lookup refs definitely a big improvement when working with data from Datomic, but :db/ident support for ref attributes would be extra tasty.

Our main use-case is the ability to share query definitions between Datomic and Datascript. We're pushing the "Datomic-as-protocol" idea as far as we can, and it's working out very well,...

We have various type "enums" which we mix and match, mainly as filters for list views. The types are also used as metadata to specify which attributes go with which...

For my case, I think it would suffice to handle only the input side of things. That avoids the necessity to pull from Datomic all of the enum entities in...

I've found away to work around this and keep things consistent on the Datomic/Datascript sides, so I'll retract my request for this feature.

I've been able to work around some of the Datomic/Datascript differences with a few small utility functions. See gist: https://gist.github.com/sparkofreason/6b3ffd63d148cd7dc37a

Not that painful, really. If it were a choice between using the utility functions or having idents but degraded Datascript perf, I'd take the first option. Personally I think the...

Yes, thanks, using edotor does help. If I can scrape together some time, I'll look into a PR. The navigable SVG used here is also handy: https://github.com/SevereOverfl0w/vizns

The first problem I had was typing `vlaad` instead of `vlaaad`. I was also a little confused because I expected the Reveal window to open when the REPL started, now...

Here's the link where @seancorfield has the init.coffee file: https://github.com/seancorfield/atom-chlorine-setup