Page 1 of 1

Timestamp / rowversion data type support?

Posted: Wed 14 Mar 2012 03:24
by nhc1987
Hi,

Is TIMESTAMP (rowversion) data type supported in dotConnect for MySQL?

We have a table with a timestamp column. Everything goes well with MS SQL but we got problem when switching to MySQL with Devart dotConnect.

We are using Entity Framework 4.2 code first and Devart dotConnect 6.7. We also tried the free Connect/NET from Oracle and got the same problem.

The detailed exception is as below

Schema specified is not valid. Errors:
(94,6) : error 0040: The Type rowversion is not qualified with a namespace or alias. Only primitive types can be used without qualification.
(155,6) : error 0040: The Type rowversion is not qualified with a namespace or alias. Only primitive types can be used without qualification.
(165,6) : error 0040: The Type rowversion is not qualified with a namespace or alias. Only primitive types can be used without qualification.


Could you guys please advice?

Regards,
Michael

Posted: Thu 15 Mar 2012 15:39
by Shalex
The .IsRowVersion() call itself for binary property sets the data type to "rowversion" if the correct database-specific data type was not set before using .HasColumnType(string).
This optimization was made for SQL Server and it is not suitable for other RDBMS because other servers do not have the "rowversion" data type. We recommend to call .IsRowVersion() only in case when .HasColumnType(string) was invoked before.

Posted: Mon 19 Mar 2012 08:04
by nhc1987
Thanks Shalex. We will try to find another way to deal with this limitation.

Re: Timestamp / rowversion data type support?

Posted: Thu 05 Mar 2015 12:27
by Shalex
The capability to create an automatically updated timestamp column via either the Timestamp attribute or the .IsTimestamp() method of Code-First fluent mapping is supported in dotConnect for MySQL starting from the 8.3.359 (26-Feb-15) build.