This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
I should probably just put this down for now, but I'm stubborn. I've got a complex pull pattern that isn't working, and I cannot for the life of me figure out why. I've got it narrowed down to a pretty minimal test case. This works:
Entire output:
user=> (:row/_columns (d/q '[:find (pull ?e [{:row/_columns [:db/id]}]) . :in $ ?e] db 277076930201266))
[{:db/id 277076930201265}]
user=> (:row/_columns (d/q '[:find (pull ?e [* {:row/_columns [:db/id]}]) . :in $ ?e] db 277076930201266))
nil
The only difference between the two is the wildcard at the top level of the pull spec. If anybody can see something I'm missing, I surely would appreciate it if you'd point it out to me.
@bhagany: do you have this isolated in a test db that you could potentially share? Or that you have schema/tx instructions for?
@bhagany: we had a similar bug reported but were unable to reproduce it with our own sample data (e.g. mbrainz) and the reporter didn’t follow up with their own data/instructions for repro.
complicating issues, the bug I’ve seen that looked similar was reported only for a test suite running against a mem db. The user didn’t report whether or not they were able to repro on durable storage.
@bkamphaus: yes, I can share it, and I'm using dev storage. Do you just need datomic.h2.db?
@bkamphaus: I hope I've got that right - I'm going to be leaving shortly for a vacation and won't be back until Tuesday. So, here's the db: https://www.dropbox.com/s/kb3f30irv1eu2z0/datomic.h2.db?dl=0
@bkamphaus: And here's the schema too, just in case: https://www.dropbox.com/s/fv30duh11ejj1kr/schema.clj?dl=0
@bhagany: easiest way to pass is just the backup/restore mechanism. e.g., $DATOMIC_DIR/bin/datomic backup-db datomic:<dev://localhost:4334/dbname> file:///path/to/dbname
No worries, @bhagany - enjoy your vacation time!