-
Notifications
You must be signed in to change notification settings - Fork 585
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
Update generates wrong SQL when running parallel #298
Comments
Any Updates for this? I have the same issue, After run this code: await DbConnection.UpdateAsync(aggregateRoot, DbTransaction); I got this is the exception:
Same as MitarNikolic, when I look at the SQL in the server profiler of "Microsoft SQL-Server management studio" you can see that wrong SQL gets generated. FYI: But unfourtunally you get the warning: |
Hi @urodriguez , just to help me, did you try to use the Sync update?? I'm asking because the SQL Generation is the same for both of them and if one works and the other don't I'll have a more restricted area to look for. Also it would help to send me the code example with the mappings |
I didn't. |
@urodriguez I asked about the test not for performance but for helping me to find the issue. If the same happens in the sync version it's 1 thing... if only in asysnc its something else |
Investigating this issue I could notice that version 1.6.3, even having a Async method always used the SYNC implementor. I'm still looking to fix it but I really need information to find the issue. |
This is the same as #306, and I have it as well. Below is a short program that causes the bug - at least on my machine in LinqPad, which throws with the message "Must declare the scalar variable "@u_3."
|
Any update on this issue ? |
Pretty sure this project is more or less abandoned :/ |
Hello everyone,
I created a XUnit test which uses DapperExtensions to update two different tables in the database.
This works perfectly fine as long as you execute the two updates one after another.
As soon as you try running them parallel, tho it generates the following exception:
Looking at the SQL in the server profiler of "Microsoft SQL-Server management studio" you can see that wrong SQL gets generated.
Kind regards
Mitar
The text was updated successfully, but these errors were encountered: