Jan Novotný
Jan Novotný
I've discussed this matter also with `o1-preview` and refined naming a little bit: - https://chatgpt.com/share/66f155c8-b5b0-800a-8f9f-afe166f62a0a Finally, I tried to let it explain what logic the final query proposal represents with...
Issue is almost done. We wait only for @lukashornych to finalize REST / GraphQL support for segments and we can also finalize the documentation.
Tip for exploration: https://github.com/benldr/JPruningRadixTrie
To evaluate: https://foojay.io/today/jvector-1-0/#VectorSearch
To read: https://db.in.tum.de/~leis/papers/ART.pdf
Again: https://github.com/jbellis/jvector
Reaction to those points: - the process will be as follows: - ParameterValue will define reference `parameterType` with attribute `order` (order of the parameter value inside parameter type) - code...
We will also have to introduce something like `ReferencePredecessor` that would be used as the inversed form of `Predecessor` used on reference. The Predecessor always contains primary key of the...
Interesting idea - the problem is not only in the query language but also in the output DTOs. We would have to have a new information in the `Entity` class...
And we'd need to also support price constraints nested inside `referenceProductsHaving` - we should have explicit functional test for this situation.