I'm migrating the data access layer of a legacy application to NH (from sprocs and raw ADO.NET) and I'm running into some difficulties with the esoteric way the legacy app handles optimistic locking. I'm reasonably confident that I could solve my problem if I am able to change the way NH generates the optimistic locking sql.
Specifically, I need to go from this: UPDATE tblExample SET Name = 'SomeNewName' WHERE ExampleId = 1 AND RowVersion = 0x0000000001132061 To this: UPDATE tblExample SET Name = 'SomeNewName' WHERE ExampleId = 1 AND RowVersion <= 0x0000000001132061 (look carefully at the row version comparison) Now theoretically I could achieve this with NH's support for custom sql but that would defeat much of the purpose of using an ORM. Can anyone tell me if there is an option/feature I can use to achieve this change, or alternatively give me some direction if they think it would be reasonably straightforward for me to add this feature to NH? Thanks! Paul Batum
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
