Possible problem with how Concurrency is use...


Author
Message
Edhy Rijo
E
StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)StrataFrame VIP (4.7K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
I have a based BO in which I have the following properties setup for all my BOs:

DeleteConcurrencyType = OptimisticRowVersion

UpdateConcurrencyType = OptimisticRowVersion

RowVersionOrTimestampColumn = "RowVersionField"





I have a couple of BO in which I don't want to use any Concurrency, so I simply setup these properties:

DeleteConcurrencyType = Off

UpdateConcurrencyType = Off

RowVersionOrTimestampColumn = "RowVersionField" (this was left in, since it should have not effect)





Problem: When trying to update a record I get the following exception:

The formal parameter "@RowVersionField" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output




So it looks like that by leaving the value in RowVersionOrTimestampColumn, will still be used even if the xxConcurrencyType properties are set to OFF, shouldn't this value be ignored when concurrency is OFF?


Edhy Rijo

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search