[Mono-dev] A bug in the latest SVN System.Data (concurrency exception)?

Kornél Pál kornelpal at gmail.com
Wed Oct 18 17:35:18 EDT 2006

>> It could solve the problem. Note that 0000-00-00 00:00:00 is an
>yep, and Mono represents it as a null value when it reads such form
>from the database (both ByteFX and the MySqlConnector)
>> invalid date so MySql may store 0001-01-01 00:00:00 using a different
>> value that is non-zero. If there is no other solution 0001-01-01
>> 00:00:00 and 0000-00-00 00:00:00 should be treated equally by the
>> connector.
>That's my guess, too. The short term solution is to set the
>timestamp/date fields to a default value of 1000-01-01 00:00:00, which
>is the minimum date value mysql accepts.

If you mean DBNull on "null" then I think there is no bug because you should 
be able to set fields to DBNull that will result in the expected zero value.


More information about the Mono-devel-list mailing list