Christian Beikov
Christian Beikov
The integration for some of the more advanced features would need to be completely rewritten. The simple stuff obviously would work by just using the query string generated by Blaze-Persistence...
AFAIU, behind the scenes reactive is just a thread pool for running the queries/IO async. Unless you do your Blaze-Persistence queries in a write transaction, you could do the fetching...
Unless you mean that you fire e.g. 3 different queries for products, related and recently viewed ones, I wouldn't bet on "parallelizing" being faster than using a single optimized query...
I see, but in that case I am pretty certain that reactive won't buy you anything here. Just running the things in parallel is good enough.
You wouldn't see exceptions but see that a wrong query is executed that then triggers lazy loading
Until I have a reproducer by @ahofmeister I can't really fix this. Tried to reproduce the case though so far I was unable to.
As I just found out, it is not possible to use default methods of a functional interface within the lambda body because of http://docs.oracle.com/javase/specs/jls/se8/html/jls-15.html#jls-15.27.2. One way around that would be...
Thanks for the reproducer, I'll look into this!
Hi @patoessy, can you give us more details please? What did you try and what didn't work? Please add some code snippets and stack traces of errors you encountered.
Hi and thanks for the report. We generate fields with the attribute names i.e. for `getReturn` the attribute name is `return` which is a keyword, so that fails at some...