Islam Aliev
Islam Aliev
Why is this issue closed? I don't think provided workaround is the most elegant solution. Shouldn't there be something more interesting?
Here is one of the use cases in my app using similar workaround: ```golang Context("if requested transactions for a specific date", func() { var ids []model.TransactionID var day1, day2, day3,...
I think it would be a nice feature. Just throwing couple more ideas: - we should execute them in random order by default, but would be nice to be able...
> Why would you want this? Why should we permit this? Most of the time you don't need it, but I can tell from my personal experience that sometimes it's...
Though this will certainly increase overall robustness, but also significantly increase time to run all the tests. I think we should anyway explicitly cover all index-related scenarios to prof not...
> Query on an indexed field should always return the same results as if the index was not there at all, and it is really really easy for us to...
That is an interesting task. We could also use the tool with our random doc generator. But generating random tests is one thing and a challenge on it's own. Another...
> Only done an quick look, nothing immediate code wise. But can you create a follow-up issue to change the `null` behavior for Numeric comparison on the Go connor implementation...
Bug bash result: created https://github.com/sourcenetwork/defradb/issues/3778
another thing I'd like to clarify before the merge: these filters on json values will ever match only if a whole json object is equal to what's in the filter,...