Locking in Visual Designer

[Nikolai Hellwig]

Is it possible to use pessimistic locking when using the Visual Designer (.rlinq files) or will it be possible in future?

I need to make a decision which way i should use (objectscope or context with modelfiles).

I already tried to use the lock function, but i get an error message: "Unsupported Operation: explicit locking in optimistic transactions"

I can't find an option in the designer to set it to pessimistic locking.

best regards

Nikolai Hellwig

[Zoran]

Hello Nikolai Hellwig,

 Yes it will be possible in the Visual Designer and the first version having the necessary UI will be released later today. We have included the Backend Configuration Settings as part of our Model Settings Dialog and there you can configure every setting of such nature like caching behavior or transaction locking. Looking forward for your feedback.

Regards,
Zoran
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Nikolai Hellwig]

I still can not get it working. My Problem is everytime i call the Lock-Function of ITransaction i get an "Unsupported Operation: explicit locking in optimistic transactions".

When i try to set: 

Scope.TransactionProperties.Concurrency = TransactionMode.PESSIMISTIC_EXPLICIT;

I get an Exception "Unsupported for Managed Transactions".

My BackendConfiguration is:

BackendConfiguration backend = new BackendConfiguration();

backend.ConnectionPool.IsolationLevel = "SERIALIZABLE";

backend.Runtime.LockSqlSuffix = "for update nowait";

Regards

Nikolai Hellwig

CHW Software GmbH

[Zoran]

Hello Nikolai Hellwig,

 Can you give us more information about the approach that you have used to obtain the objects scope in a project created with the Visual Designer. We tried to reproduce the same exception by obtaining the scope from the context but we were not able to do so. We are looking forward towards further collaborating on this issue and finally solving it.

Regards,
Zoran
the Telerik team