Jeremy Taylor

> You are still going to run out of memory for this query quite often (which should now no longer cause a leak), but this is related and should be...

Thanks for opening the issue @esp1 - you can use `CAST(foo AS text)` in many cases, does it work for your needs? For complex types you will get a cast...

Workaround example for `name`: `SUBSTRING('user/id' FROM POSITION('/' IN 'user/id') + 1)` [Play](https://play.xtdb.com/?version=2.0.0-b1&type=sql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6IklOU0VSVCBJTlRPIGRvY3MgKF9pZCwgZm9vKSBWQUxVRVMgKDEsICdiYXInKSJ9XQ%3D%3D&query=U0VMRUNUIFNVQlNUUklORygndXNlci9pZCcgRlJPTSBQT1NJVElPTignLycgSU4gJ3VzZXIvaWQnKSArIDEpLCBmb28gRlJPTSBkb2Nz)

Workaround example for `namespace`:`SUBSTRING('user.abc/id' FROM 1 FOR POSITION('/' IN 'user.abc/id') - 1)` [Play](https://play.xtdb.com/?version=2.0.0-b1&type=sql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6IklOU0VSVCBJTlRPIGRvY3MgKF9pZCwgZm9vKSBWQUxVRVMgKDEsICdiYXInKSJ9XQ%3D%3D&query=U0VMRUNUIFNVQlNUUklORygndXNlci5hYmMvaWQnIEZST00gMSBGT1IgUE9TSVRJT04oJy8nIElOICd1c2VyLmFiYy9pZCcpIC0gMSkgQVMgbmFtZXNwYWNlX3BhcnQ7)

The `cast` function is definitely already available in XTQL but I can't see that we have a way of referring to the target types using literals/strings yet, e.g. [Play](https://play.xtdb.com/?version=2.0.0-b1&type=xtql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6Ils6cHV0LWRvY3MgOmRvY3Mgezp4dC9pZCAxIDpmb28gXCJiYXJcIn1dIn1d&query=KC0%2BIChmcm9tIDpkb2NzIFt4dC9pZCBmb29dKQogICh3aXRoIHs6YmFyIChjYXN0IHh0L2lkIDp0ZXh0KX0pKQ%3D%3D) The...

@jarohen would this issue also cover lexicographical sorting of text (or URLs...)? - needed for Clickbench: ``` xtdb=> SELECT SearchPhrase, MIN(URL), COUNT(*) AS c FROM hits WHERE URL LIKE '%google%'...

Sure thing. Would you prefer them commented out on main for now? Or on a branch?

How about `ERROR: invalid transaction - total transaction size is larger (XXX bytes) than the configured maximum transaction size (YYY bytes)`

Fair, the user can probably connect the dots from seeing `RecordTooLargeException` as-is.

Fwiw, users have a similar experience when hitting `No space left on device` behind the scenes (e.g. running a fully local node without remote object storage) - the submit error...