Error - Default value (systimestamp) is not valid for DateTi

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
Emily
Posts: 13
Joined: Mon 30 Nov 2009 23:45

Error - Default value (systimestamp) is not valid for DateTi

Post by Emily » Tue 01 Dec 2009 00:18

Default value (systimestamp ) is not valid for DateTimeOffset. The value must be in the form 'yyyy-MM-dd HH:mm:ss.fffffffz'.

----------------------

I just upgraded to the latest dotConnect version (5.35) and when using the latest EF Developer (2.50.50), I get the above error when dropping a table from Oracle with a timestamp field. This error was not being generated in the previous version.

FYI, the field in the Oracle table has default value set to 'systimestamp' and is of type 'TIMESTAMP(6) WITH TIME ZONE'.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Tue 01 Dec 2009 14:36

Thank you for the report.
I will let you know about the results of our investigation.

Emily
Posts: 13
Joined: Mon 30 Nov 2009 23:45

Post by Emily » Wed 09 Dec 2009 20:55

Devart,

Any update on this issue? With this error in place, I can't seem to use your EDM Designer due to always erroring out.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Thu 10 Dec 2009 16:36

We are working on this issue.
I will let you know as soon as it is fixed.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Thu 10 Dec 2009 16:43

As a temporary workaround you can clear the default value and set StoreGeneratedPattern to Identity in your Entity Framework model.

Emily
Posts: 13
Joined: Mon 30 Nov 2009 23:45

Post by Emily » Fri 15 Jan 2010 21:23

I just downloaded the latest version today and this problem still persists. Any update on this issue?

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Mon 18 Jan 2010 10:55

I will let you know as soon as the problem is fixed.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Fri 29 Jan 2010 15:19

The problem is fixed. Look forward to the next build.

Post Reply