@brian.rogers I think you want to look at having an API Gateway proxy resource and configuring the ion with the API Gateway :integration, in that way your whole request path will be available in the context object. I haven’t gotten to revisit ions and API Gateway in months so this is faint memory backed up by a quick review of the docs page.

Re: my problem above--I've taken out all the deps that were easy to take out, but no dice. I'm going to see if I can somehow replace a large-but-important dep I have and hope that works. However, is it possible on the solo topology to upgrade the compute stack to use a larger ec2 instance instead of the default t3.small? (I'm assuming that would fix the issue). I'd upgrade to production topology, except I just can't afford two i3.large instances at the early stage I'm in right now.

I got stuck a bit with the following problem. When shifting a predicate clause inside not, the query stops working. For example, this query works fine:

[:find ?e ?id
 :where
 [?e :user/pg-id ?id]
 [(< ?id 5)]]

[:find ?e ?id
 :where
 [?e :user/pg-id ?id]
 (not [(< ?id 5)])]

The error message I’m getting in console is

processing rule: (q__198 ?e ?id), message: processing clause: ["not" [(< ?id 5)]], message: :db.error/invalid-lookup-ref Invalid list form: [(< ?id 5)]

What's a good way of getting secrets up on to datomic cloud? (details here: https://ask.clojure.org/index.php/8554/how-to-store-secrets-in-datomic-cloud)

Thanks @chris_johnson!

I’m trying to deploy a Datomic Ion application and it’s failing in datomic.client.api/client (creating the client).

{
 "Type": "java.lang.AssertionError",
 "Message": "Assert failed: cfg",
 "At": [
        "datomic.client.impl.local$create_client",
        "invokeStatic",
        "local.clj",
        208
        ]
 }

@adamtait https://docs.datomic.com/cloud/troubleshooting.html#assert-failed

I lost a day to this same error message about 2 weeks ago.

Hey y'all 👋 . I'm curious to hear y'all's opinion about when you would choose to use a Datomic enum as opposed to a keyword. One obvious distinction is that an enum is only suitable for a closed set, but are there other factors you consider? What if you have a closed set in terms of what values can be added at any given time, but expect that set to potentially grow in the future? Thanks!

datomic has enums?

performance on heterogenous vs homogenous tuples Say I have a tuple of [type spec], where both values are strings. This vector is guaranteed to be length = 2. I can model this as a homogenous tuple of strings - :db/tupleType :db.type/string or a heterogenous tuple - :db/tupleTypes [:db.type/string :db.type/string] I suspect performance+storage will be better on the homogenous tuple. However, the heterogenous tuple more accurately models the data as it forces count = 2. Are these correct assumptions?