Mapping sql Time type to TimeSpan

[Christian]

I'm working with Time type in SQL Server, and when I map this field to OpenAccess it creates a DateTime field. Is there any way to map this as TimeSpan?
Thanks

[Chris]

I'm having the same issue. Using MySQL's time data type gets interpreted as DateTime. I can manually change the generated code to be c# TimeSpan type but anytime I change the rlinq map it gets overwritten.

[Ady]

Hi Christian,

 After generating the domain model from the database you can select the particular property in the designer and change the CLR type of this property to 'TimeSpan' in the properties window. 'TimeSpan' is not listed there but you can just type it in.
Querying for data should then give you TimeSpan values.

@Chris - You should change the CLR type in the designer and save the rlinq file. This will generate the right CLR type in the code. Do not change the generated code directly because this is always regenerated everytime you save the rlinq file.

Regards,
Ady
Telerik

[Chris]

Thanks Ady! That worked. It wasn't one of the options in the drop down but I see now you can free type your CLR data type. Great stuff.

[Christian]

Thanks Ady, it worked! 
Do I have to change it every time I regenerate the Domain Model? 

[Ady]

Hi Christian,

 Glad to know that it works for you. 
No, you do not need to set it every time. Its like any other property - you need to set it only once.

Regards,
Ady
Telerik

[Evo]

Hi Ady,

I'm having troubles when SaveChanges is called with TimeSpan (the field is mapped in the database as Time)

Additional information: Insert of 'xxxx-' failed: Telerik.OpenAccess.RT.sql.SQLException: Operand type clash: int is incompatible with time
Statement(s) could not be prepared. ---> System.Data.SqlClient.SqlException: Operand type clash: int is incompatible with time

Is there something I'm not mapping correctly?

Thanks in advance.

[Ady]

Hi Evaristo,

I was able to reproduce the error and have created a bug entry for the same. Unfortunately there is no workaround for this problem.

You can use the 'System.DateTime' as the CLR type for a 'time' column or map the 'TimeSpan' field to a 'datetime' column.

Regards,
Ady
Telerik