You might be running into some desync issues with the db atom in your state. https://github.com/roterski/fulcro-rad-xtdb/blob/main/src/main/roterski/fulcro/rad/database_adapters/xtdb/wrap_xtdb_save.clj#L148 Just a guess though. Not a high degree of confidence that this is your issue.

I didn't understand how to use the times in the query, and that they are sticky in the web console. I have it working perfectly now so I can read-only query into the documents created from the app. Really excellent system so far. I look forward to learning more xtdb.

Glad to hear, thanks for keeping us all posted :)

@UAB2NMK25 the fulcro-rad-xtdb plugin uses a https://docs.xtdb.com/language-reference/datalog-transactions/#transaction-functions named ::delta-update to perform writes. That means delta-update needs to be present in the db as a separate entity. If you follow https://github.com/fulcrologic/fulcro-rad-demo/blob/develop/src/xtdb/com/example/components/xtdb.clj#L9 and use start-databases then https://github.com/roterski/fulcro-rad-xtdb/blob/main/src/main/roterski/fulcro/rad/database_adapters/xtdb/start_databases.clj#L27-L28 this transaction function as a part of the initialisation process but it looks like you’re missing it so I’m not sure if you’re calling this start-databases or you’re starting the xtdb node manually somewhere else - that’s would be fine but you’d need to insert this transaction function manually as well to use the plugin’s writes. UPDATE: I reread your problem and now I get that it was about querying for that function from the web console, so my answer is not very relevant. 😅 sorry for the confusion

Yes I have that transaction function, my issue was the xtdb web console, not the fulcro app. The fulcro app worked great, I was just struggling with how to properly query documents by valid time and transaction time in the console. It's all resolved though and working well now.