Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This is only guessing...</p> <p>The data driver is using a different sql connection than your plugin. So your code runs in a different transaction (or without one), and is conflicting with the uncommited changes from the data driver, resulting in a dead lock.</p> <p>Solution ideas:</p> <ul> <li>Make your code use the same connection as the data driver. This would require that the connection is somehow provided to the plugins. And you'd need a way to make the entity model use it (never worked with the entity model my self). This would be the nicest solution. You stuff would automatically participate in the transaction, with all the nice consequences like consistency and such.</li> <li>Try to ensure that both connections run in the same transaction. This would theoretically be possible using <code>System.Transactions</code>. This also requires adapting the data driver to use the <code>System.Transactions</code> model. I doubt that the two connections would see each others changes that way, so this probably won't work.</li> <li>Don't use transactions. You might be able to instruct the database server to ignore transactions, so you don't need changes to the data driver. This would work. Of course transactions were invented for a reason...</li> </ul> <p>I would go for the first one. Figure out how you can tell the entity model to use a particular sql connection and then ask the data driver developers to give it to you. This might even result in a better performance since fewer connections are required.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload