Concurrencty and version field set to timestamp

[Jason]

Hi Guys

I am trying to set up some tables with a concurrency mode of "Version" in the rlinq designer

to do this I
1) create a domain class with a field "rv" of type Int64 (as when i try Int32 it complains when i go to deploy to the server)
2) map this class to a table with a field "rv" of type bigint
3) map the class field to the table field.

When i go to deploy, the table in the database has rv of type timestamp. this just seems wrong as i have defined it as int64 and as far as I know you cant use timestamp for versioning.

Any assistance would be appriciated

[Zoran]

Hello Jason,

 This unfortunately is a behavior that we were not able to reproduce. In my test, I also created a table with a bigint column and mapped it to an Int64 property called RV. Then i selected the concurrency mode for the entity to be 'Version' and I selected the concurrency member to be RV. The SQL script generated by the Update Database From Model wizard was correct. Is there something we have missed, or could you give us more information on the scenario you are having or the exact steps to reproduce. Also, I used MS SQL Server for my testing.

Best wishes,
Zoran
the Telerik team

[Jason]

Thanks for the reply. I worked out what I was doing wrong.

In the Edit / Create Dialogue, i was checking the "Version Field" Checkbox for the rv field. If i have that checked it seems to force the field to be a timestamp no matter what I have the SQL Type set to.

Cheers
Jason

[Zoran]

Hi Jason,

 Yes that is definitely the cause. The issue is that when version is set on the column directly, this column is treated as a backend specific version column which for the SQL Server backend is a timestamp. However, setting the version setting on the property that is mapped to the column, means that OpenAccess will manage this property as the version property, thus using incremental Int64 numbers to set the version. We, on our side should put more effort to make this more transparent and better explained in the documentation. Thanks a lot for presenting this issue to us.

Best wishes,
Zoran
the Telerik team