This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-20
Channels
- # announcements (16)
- # babashka (71)
- # beginners (121)
- # bristol-clojurians (2)
- # calva (55)
- # clj-kondo (16)
- # clojure (103)
- # clojure-europe (9)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-spec (49)
- # clojure-uk (57)
- # clojurescript (28)
- # conjure (9)
- # cursive (6)
- # datascript (3)
- # datomic (35)
- # duct (20)
- # events (3)
- # figwheel-main (12)
- # fulcro (6)
- # graalvm (12)
- # juxt (3)
- # kaocha (5)
- # lumo (10)
- # malli (5)
- # off-topic (54)
- # pathom (8)
- # re-frame (19)
- # reitit (21)
- # remote-jobs (1)
- # shadow-cljs (102)
- # sql (38)
- # tools-deps (60)
- # uncomplicate (3)
- # xtdb (10)
Hello 👋 is there a way to get the entity ID of a entity that was created using the clojure d/transact
function? The function returns the tempids, but I need the actual entity IDs as I use these as unique identifiers and need a reference to a user I just created.
@lukasmoench1113 the return from transact
includes a :tempids
map that provides the mapping from the tempids to the final entity IDs
I get the following error while trying to upgrade datomic cloud storage. Is it known?
The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions.
Hey I'm trying to get a codebuild instance to be able to push up ions with datomic cloud. What permissions would the codebuild role need in order to run {:op 'push'}
?
@marshall I was able to upgrade my (all 44) lambdas using the aws cli tools, and then I could update my other compute node. But the one I started with, got stuck in UPDATE_ROLLBACK_FAILED
, and then I can't rerun the upgrade. The rollback also fails, because the old version is ofcourse also using old nodejs, and is not allowed to proceed anymore.
@maxt can you please file a support ticket (<mailto:[email protected]|[email protected]>) Manually altering components of the system is not recommended and we may need to help you work through how to resolve that
upgrading the system overall (storage stack and compute stack) should have done it automatically for you
I'm running across a strange problem. I have this in my schema (abbreviated):
{:db/ident :length/mm
:db/valueType :db.type/double
:db/cardinality :db.cardinality/one}
{:db/ident :dash-space/mm
:db/valueType :db.type/tuple
:db/tupleAttrs [:length/mm :length/mm]
:db/cardinality :db.cardinality/one
:db/unique :db.unique/value}
I never transact :dash-space/mm
, but I do transact other things like:
{:radius/key unique-string-1 :length/mm 254.0}
{:length/key unique-string-2 :length/mm 254.0}
At some point (still more digging required) I get a unique constraint error on :dash-space/mm
for the values of [254.0 254.0]
. I can't say I really understand this problem. Getting rid of :dash-space/mm
in the schema does eliminate it, but I assume there's something incorrect about the use of :db/tupleAttrs
above, right?your :`dash-space/mm` attribute is automatically created on any entity with either of the attrs in the :db/tupleAttrs
vector
because you have it set to :db.unique/value
if you ever try to transact data that would create a composite with the same value (254 254 in this case), you get the unique value error
all that said, i'm not sure the purpose of making a composite tuple with a repeated attr
if you just wanted a tuple that would hold two arbitrary longs, unrelated to other attributes on that entity, you'd need to use :db/tupleTypes
or :db/tupleType
FYI, I didn't create this part of the schema so I can't say why it was done this way
I suspect it's trying to capture the length of the dash and space, and place a unique constraint on the pair of values (which are really references)
incidentally, using doubles as identity is pretty iffy; given the semantics of doubles / precision / comparison /etc, i'd definitely be wary of using them as any kind of identifier Thanks to @alexmiller for mentioning it
Oh, I'm aware, thanks. The values shouldn't have a unique constraint. This is definitely an error on our part
#rebl and Datomic dev-local are now free as part of Cognitect dev-tools https://cognitect.com/dev-tools/