Clojurians Log v2

Hey @esp1 I can't think of anything to suggest which might be going wrong 🤔 that example seems to work fine https://play.xtdb.com/?version=2.0.0-b1&type=xtql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6Ils6cHV0LWRvY3MgOmRvY3Mgezp4dC9pZCAxMDAgOmZvbyBcImhlbGxvXCJ9XSJ9XQ%3D%3D&query=KGZyb20gOmRvY3MgWypdKQ%3D%3D Is it possible you're accidentally running against two entirely different nodes?

no, i'm definitely using the same node. i can try this on the docker version of xtdb and see if it works. if so, maybe this is just an issue with the in-memory node?

oh i also just noticed there is a beta2 out, maybe i can try that too

the Play environment is just spinning up in-memory nodes also, so there shouldn't be a difference there, but yes using the Docker image helps to rule out any JVM shenanigans at least

i just upgraded to 2.0.0-beta2 and it works now!

aha, how random, not sure what could have changed(!)

out of interest, have you used HoneySQL much before? are you strongly preferring the idea of XTQL?

thanks for looking into this with me, i appreciate you giving me the sanity check on the Play environment

Play is still using beta1 though 😅 I would love to understand what happened, but I'll leave that for another day

i've only used honeySQL a little, so i'm probably not the best person to give a representative opinion. i like the idea of constructing queries from data structures instead of strings, but both honeySQL and XTQL will do that for you

in clojure-land i've probably used datomic more than sql lately, so having a different query syntax like XTQL is ok by me, but again i may not be representative of the community

that said, i really do like the psql compatibility that xtdb offers. i've done way more sql than datomic back in the day.

@taylor.jeremydavid oh i just realized what happened! if i use the table :my-table instead of :docs, the wildcard query doesn't work: https://play.xtdb.com/?version=2.0.0-b1&type=xtql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6Ils6cHV0LWRvY3MgOm15LXRhYmxlIHs6eHQvaWQgMTAwIDpmb28gXCJoZWxsb1wifV0ifV0%3D&query=KGZyb20gOm15LXRhYmxlIFsqXSk%3D

i guess xtdb doesn't like hyphenated table names?

ah yes, of course, the name is being 'normalized' for SQL compatibility, so the hyphen becomes an https://play.xtdb.com/?version=2.0.0-b1&type=xtql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6Ils6cHV0LWRvY3MgOm15LXRhYmxlIHs6eHQvaWQgMTAwIDpmb28gXCJoZWxsb1wifV0ifV0%3D&query=KGZyb20gOm15X3RhYmxlIFsqXSk%3D that then can't be losslessly roundtripped - an unfortunate edge case 🤔

well spotted

that's fine, i can use different table names. might be good to call this out in the docs tho if it can't be worked around.

> is there a way to list the databases/tables in xtdb? yep! like any SQL-spec-compliant database we offer https://play.xtdb.com/?version=2.0.0-b1&type=sql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6IklOU0VSVCBJTlRPIGRvY3MgKF9pZCwgZm9vKSBWQUxVRVMgKDEsICdiYXInKSJ9XQ%3D%3D&query=U0VMRUNUICogRlJPTSBpbmZvcm1hdGlvbl9zY2hlbWEudGFibGVz tables for this kind of metadata (there's also pg_catalog) - there was a note about this in the docs a few weeks back but it seems it's been lost along the way > is there a way to export/import data or backup/restore an xtdb database? pg_dump would work ideally (we actually haven't tried it yet to see what's missing in the compatibility layer), but currently you need to write your own SQL (/XTQL) manually for this. You should also be able to rely purely on backups of the storage backends for backup/restore - just make sure that the tx-log backup is newer than the object-store backup (whilst also taking into account any configured tx-log retention window), or pause the system

but also on the backup/restore, most importantly, please get in touch before you attempt to roll out v2 into production 🙂 (prior to GA, anyway)

sounds good, thank you!