on 2018 Feb 15 4:00 PM
Hi, is there possibility to set isolation level for OData producer to snapshot? The isolation level parameter in ODBC is ignored and level is always set to 1. This use a read locks and we get deadlocks on concurrent update operations. thanks Miro
OData producer checks and sets its isolation level depending on the request. For example, updates and deletes use "repeatable read". The default is "read committed".
At present there is no way to request a minimum isolation level. If it is causing deadlocks, we would consider that a problem.
OData requests are atomic in that they always end in either a commit or a rollback.
Can you give me a simple repro or a more detailed explanation on how the deadlock is occurring?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
11 | |
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.