Lucy Egan
Lucy Egan
Not sure if this is exactly what your looking for but wouldn't the above use case be handled by a unique index on `company `.`name`?
To note that casting the script function number will fix the issue ``` CREATE indexTest3:jsNumber CONTENT { number: function(){return 0} }; ``` Makes the above test case return the following...
+1 Also blocks issue - https://github.com/surrealdb/surrealdb.js/issues/139 @tobiemh has there been any movement on this for surreal 2.0? Also is there a public roadmap of core things planned like we had...
Ran into this while trying to delete 160k records. experience so far is cpu usage maxed a core and memory ran away until killed, 0 records were actually deleted when...
+1, Remains the same in `2.0.0-alpha.5 for linux on x86_64` ``` CREATE test:cake; DELETE ONLY test:cake; ``` `'Expected a single result output when using the ONLY keyword'` To get the...
Another thing related to rate limiting could be the max number of live queries a ip/scoped can have open so they cant build up 100k "low cost" live queries over...
Nice catch @tobiemh - further to this, heres a minimal example, as looks like its all floats, even indexing on a `TYPE` float `FIELD` (ive only got access to alpha.8...
@emmanuel-keller If you have `DEFINE FIELD number ON TABLE test TYPE decimal;` to tell it the type of the field to be `decimal` rather than `any` then ``` CREATE test:int...
Adding extra nothing(0) precision information to dec makes them different too in a index