THAT IS AWESOME, thanks!

Keith Chisarik

Yeah, I would recommend using row versioning over the all fields concurrency.  So, either use row versioning with DB2 or just turn all concurrency checking off if you don't have a need for it or you don't care about it. 

As for needing sprocs for the updates, you don't have to have them for row versioning... you just need an extra int column to store off the row version.  Then put the name of that column in the RowVersionOrTimestamp column property on the business object and the BO will take care of the rest.

yes it was exactly what i was looking for confirmation of, thank you very much.



Is is safe to assume that OptimisticAllFields could lead to significant performance issues, hence why you suggest row versioning in your classes and documentation?



If I want that with DB2 I would have to write my own update sprocs eh?



Thanks.




Keith Chisarik

The default settings are the same for DB2 as they are for SQL Server... UpdateConcurrencyType is set to OptimisticAllFields and the DeleteConcurrencyType is set to Off.

Is that what you were wondering?

What are the default CRUD settings when using the SF DB2 Client? specifically as they relate to concurrency.

Keith Chisarik