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
|
Hi I concluded dat you used optimistic concurrency ? update id,field1,field2 where id=,field1=,field2= Maybe it's not best practise but i want : update id,field1,field2 where id= update statements.. 2nd small question is with KeyTable does the "UPDLOCK" guarantee mee that no key is given out twice ? Never seen that construction...
|
|
|
Hi juulepuul, What SQL are you seeing? Optimistic concurrency is only enabled when you have a field called lockVersion in your model class. Normally, the generated updates are like the ones you want. Regarding UPDLOCK, yes, this is analogous to FOR UPDATE on other databases. It locks the row(s) so that key generation is serializable. Cheers, Andrew. |
|
|
Hi thanks for the fast reply..
Somehow this product is way more simple than say hibernate while ate some fronts you even have more features.. (Implementation of data binding interfaces etc). you have a new customer :D
|
|
|
Thanks, glad you like it :-) |
|