there’s no way to forward-declare an entity ref, right? i can’t tx data into a db like {:foo/bar [:bar/id 123]} where bar/id (and the associated entity) don’t yet exist in the db?

you can assert a nested entity, thereby creating it

{:foo/bar {:bar/id 123}}

@lwhorton ^ however, if you are using a lookup ref then yes, the entity needs to exist already

ah, cool. i guess i need to order my etl properly

@lwhorton see https://docs.datomic.com/cloud/transactions/transaction-data-reference.html#sec-7-1 about referencing other entities created within the same transaction

Is there a dictionary of Datomic errors? This one is currently inscrutable to me:

{
                "Type": "clojure.lang.ExceptionInfo",
                "Message": "Server Error",
                "Data": {
                    "CognitectAnomaliesCategory": "CognitectAnomaliesFault",
                    "CognitectAnomaliesMessage": "Server Error",
                    "DatomicAnomaliesError": {
                        "Error": "Unable to create catalog entry",
                        "Cause": {
                            "Conflict": true
                        }
                    }
                }

@grzm solo or production?

solo, but seen in production as well

can you file a ticket on the support portal so we can investigate?

Will do.

what’s the conventional “last step” after a query w/ entity pull to get the entities as a collection instead of a collection of single-entry collections? do we just use mapcat?

@lwhorton re forward declaration: I learned a trick for this. all my entities have a shared uuid attribute. just before the save, I copy the str version of the uuid into the :db/id as a “temp-id”. this means that all references to that entity can now also use the string version in their ref attrs and Datomic will resolve them