This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
LOVE Lightspeed, and im really enjoying usng it... But its time for me to bug you guys again... I would like to Use optamistic concurrency locking (ONLY if the user upgrades to a multi-user system) , by default there will be only a single user, so the overhead of checking/updating columns is not necessary. Normally a Column is added to each table where you want to use optamistic concurrency locking (LockVersion). Therefore i'll have to always add that column, which is ok, but how do I "disable" / "enable" the locking functionality at runtime? The same applies to Default namingstrategy. This functionality needs to disabled/enabled at runtime in code.
thx Anthony |
|
|
|
|
Hi Anthony [quote user="antprog"]I would like to Use optamistic concurrency locking (ONLY if the user upgrades to a multi-user system) , by default there will be only a single user, so the overhead of checking/updating columns is not necessary. Normally a Column is added to each table where you want to use optamistic concurrency locking (LockVersion). Therefore i'll have to always add that column, which is ok, but how do I "disable" / "enable" the locking functionality at runtime?[/quote] There is currently no way to disable optimistic concurrency in this way. The perf overhead is minimal but we could look at adding this feature if you are still concerned. [quote user="antprog"]The same applies to Default namingstrategy. This functionality needs to disabled/enabled at runtime in code.[/quote] I'm not sure I follow you on this one. DefaultNamingStrategy is simply the default name resolution scheme. You can override it by implementing INamingStrategy. Please clarify if I've misunderstood. Cheers, Andrew. |
|
|
|
|
Hi Andrew, The concurreny issue is not critical, im just a performance freak.... The other issue is realted to being able to enable/disable the CreatedOn,UpdatedOn,DeletedOn columns for a table from withing code. Cheers Anthony |
|
|
|
