-
Notifications
You must be signed in to change notification settings - Fork 933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Cacheable Multicriteria/Future'd query with aliased join throw exception #1733
Conversation
Better take the habit of generating async code within each commit. |
@fredericDelaporte I did and it failed. Parking that part until I finalise the tests. |
If description is correct:
I believe with new batcher #1718 Future is not affected by this issue (as |
Maybe the regen fails due to maca88/AsyncGenerator#70. You would have to try with methods instead of delegate parameters. @bahusoid, interesting indeed. But of course better checking that with appropriate tests, so having them thanks to this PR ist still a good thing. Maybe you could then cherry-pick them in #1718 for ascertaining it does also fix #1344. |
@bahusoid That's good news. I ran the tests against your branch and 3 of the 5 tests still fail. I can push a PR to your repo to show you what I mean? There still a problem with And the |
New batcher is used only with Future methods. MultiCriteria and MultiQuery are separate batchers. If you need MulitCriteria or MultiQuery - you still need to fix it. |
9259f4e
to
a1b6a56
Compare
Is #383 the same? |
Not sure if this question is directed at me. I'm not comfortable enough to answer it convincingly. |
@igitur its to whomever capable to answer this question. |
85a4cef
to
0de7af4
Compare
@maca88 I see you've been commenting on related PRs. Just, FYI, my goal for this PR was to enable caching when using |
This is a bug in query batch implementation indeed. It should be fixed with #1789.
This would change with #1783, by obsoleting Multi-Criteria/Query APIs in favor of using the query batcher. Those tests should be converted for using the query batcher.
They could have the same root cause. |
# Conflicts: # src/NHibernate.Test/NHibernate.Test.csproj
0de7af4
to
5f3efb7
Compare
With #1783, the flawed class is now obsoleted. |
Original Jira post at https://nhibernate.jira.com/browse/NH-3864
Subsequent issue filed at #1344
I'm adding the unit tests that I found first. I don't have a fix yet, but I'm willing to have a bash at it.