Hi, I am getting a :db.error/not-an-entity Unable to resolve entity: error and I have no idea how to debug this 😇, where should I start looking?

any pointers would be greatly appreciated. TIA

@thomas that usually means you're trying to resolve something that doesn't exist. e.g. a typo'd entity name in [:some-id "Fobar"]

What's the value of using Datomic's :db.type/uri instead of putting a string in there? The only thing I'll ever do when pulling the data out again is to put it into cemerick/url which is happy with strings

I have the same approach to UUIDs, seems wildly more convenient to just use a string since most of the time the UUID comes from a URL and is a string anyway. And then I don't have to convert it to an UUID, return 404 instead of 500 in my web API if it's an invalid UUID, etc

yep, that was my thinking. like how i used to put longs in SQL dbs to represent timestamps (as ms since the epoch) instead of using built-in timestamp types

I always use the types because types.

UUIDs do have a more compact representation in datomic (really fressian) than strings. But for URIs there is really no difference except type.

date types in dbs are my pet peeve

yeah, java util date is just not enough

so fun converting that stuff back and forth to no end

I have a (still unrealized) plan to encode all the xsd date and time types into a long with canonical sorting

we really hurt for "vague human" date types

e.g. LocalDate LocalTime LocalDateTime, etc. where there is no time zone and it's not timestamp-resolution

or sometimes where there is a zone, but it's not timestamp resolution

we encoded dates (i.e. Y-M-D values) into a java util date, and that was a huge mistake. we should have just used strings

we were promised custom datatypes in datomic eventually. does anyone know how that is progressing?

Anyone know if this is expected behavior?

(d/q '[:find [(pull ?e [:some/attr]) ?e] :where [?e :some/attr]] db)

ArrayIndexOutOfBoundsException   [trace missing]

whereas.. something like this works fine:

(d/q '[:find [(pull ?e [:some/attr]) ?tx] :where [?e :some/attr _ ?tx]] db)

@matthavener Yes, that is a known behavior; you can’t get both e and a pull on e in the same find spec

interesting! Thank you

you can, however pull both :some/attr and :db/id if you need to

right

I'm having troubles connecting console to my local datomic-pro running with a mysql storage. I'm using the following command from the datomic directory:

bin/console -p 8888 dev datomic:sql://\?jdbc:

mysql lib may not be on classpath

console live datomic:sql://\?jdbc:postgresql://${docker_postgres_datomic_host}:${docker_postgres_datomic_port}/${docker_postgres_datomic_db}\?user=${docker_postgres_datomic_user}\&password=${docker_postgres_datomic_pass}

@favila the mysql lib is in the lib folder and the transactor connects successfully? does it need to be somewhere else?

logs or console may have a better error message

no, that should be enough

Are you missing the mysql db ?

@foobar that was it! duh!

i assumed it worked like the peer

trying to setup health checking datomic using ping-host/ping-port configuration, but getting following stacktrace error: bin/transactor ~/projects/abraxas/transactor/config/dev-transactor.properties Launching with Java options -server -Xms1g -Xmx1g -XX:+UseG1GC -XX:MaxGCPauseMillis=50 Critical failure, cannot continue: Error starting transactor java.lang.RuntimeException: Unable to start ping endpoint localhost:9999 at datomic.transactor_ext$start_ping_endpoint.invokeStatic(transactor_ext.clj:42) at datomic.transactor_ext$start_ping_endpoint.invoke(transactor_ext.clj:25) at datomic.transactor_ext$start_pro.invokeStatic(transactor_ext.clj:63) at datomic.transactor_ext$start_pro.invoke(transactor_ext.clj:59) at clojure.lang.Var.invoke(Var.java:379) at datomic.transactor$run_STAR_.invokeStatic(transactor.clj:294) at datomic.transactor$run_STAR_.invoke(transactor.clj:220) at datomic.transactor$run$fn__23373.invoke(transactor.clj:347) at clojure.core$binding_conveyor_fn$fn__6757.invoke(core.clj:2020) at clojure.lang.AFn.call(AFn.java:18) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Insufficient threads: max=3 < needed(acceptors=1 + selectors=2 + request=1) at org.eclipse.jetty.server.Server.doStart(Server.java:368) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at cognitect.http_endpoint.jetty$start.invokeStatic(jetty.clj:123) at cognitect.http_endpoint.jetty$start.invoke(jetty.clj:120) at cognitect.http_endpoint.jetty$server$fn__21184.invoke(jetty.clj:136) at cognitect.http_endpoint$create_endpoint.invokeStatic(http_endpoint.clj:292) at cognitect.http_endpoint$create_endpoint.invoke(http_endpoint.clj:217) at cognitect.nano_impl.server$create.invokeStatic(server.clj:172) at cognitect.nano_impl.server$create.invoke(server.clj:141) at cognitect.nano_impl$create.invokeStatic(nano_impl.clj:166) at cognitect.nano_impl$create.invoke(nano_impl.clj:96) at datomic.transactor_ext$start_ping_endpoint.invokeStatic(transactor_ext.clj:33) ... 13 more

@fenton what version of datomic?

@marshall datomic-pro-0.9.5561.62

is something else using that port on your machine?

hrm. hang one

that insufficient thread bug should have been fixed in http://docs.datomic.com/changes.html#0.9.5561.59

@marshall yet i'm on the later version...hmmm...

regression?

i am running in dev mode...

config follows:

@fenton can you email <mailto:[email protected]|[email protected]> with your issue and your config files (redacted of any sensitive info) as well as the number of cores on your system (real & virtual)

i.e. getconf _NPROCESSORS_ONLN

or the contents of /proc/cpuinfo if you’re in linux

@marshall ok will do thx.

http://docs.datomic.com/changes.html#0.9.5561.59

oops

🙂