This project is read-only.


No timestamp validation is performed during the conversion.


sqlite allows default timestamp values like:
"0000-00-00 00:00:00" (which are bad DateTime objects, but that is another issue)
"0001-01-01 00:00:00" (which are valid DateTime objects)
However, these values are invalid SqlDateTime objects (corresponding to the SqlServer timestamps). The conversion utility does not validate the default values at all.
Next, when the actual data is converted, these default values prevent the conversion for the same reasons.
Closed Feb 25, 2012 at 2:16 AM by abub
Closing this as a won't fix because the problem is in the C# port of SQLite: System.Data.Sqlite DLL throws StringFormatException with Message that says "String was not recognized as a valid DateTime" for time values that are less than the ones supported by .Net framework. The exception does not have the actual value in it anywhere and the problem is that this execption can occur because of other reasons as well. Catching the exception and handling it does not work. System.Data.Sqlite needs to be modified or SQLite itself need to address this issue in their code and then handle the exception


abub wrote Jan 24, 2012 at 5:20 AM

Thanks for reporting this. We are looking into it right now.

wrote Feb 25, 2012 at 2:16 AM

wrote Feb 13, 2013 at 9:38 PM

wrote May 16, 2013 at 5:37 AM