[Mono-bugs] [Bug 77268][Wis] Changed - Sqlite DateTime Parameters Handled Incorrectly

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tauberer at for.net.

http://bugzilla.ximian.com/show_bug.cgi?id=77268

--- shadow/77268	2006-01-15 14:51:02.000000000 -0500
+++ shadow/77268.tmp.29918	2006-03-08 08:44:42.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 77268
 Product: Mono: Class Libraries
 Version: 1.1
 OS: All
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Wishlist
 Component: Sys.Data.SqlClient
 AssignedTo: tsenganal at novell.com                            
 ReportedBy: jhill at arcfocus.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -136,6 +136,16 @@
   dt.Columns.Add("DateField");
 will load the column as an Int64 value, rather than a DateTime.
 
 My guess would be that the best way to pass DateTime values into sqlite
 would be as strings of the format "yyyy-MM-dd HH:mm:ss" ; however, perhaps
 there is a more correct/efficient/precise way to do this.
+
+------- Additional Comments From tauberer at for.net  2006-03-08 08:44 -------
+Storing them as strings makes recalling them as DateTimes extremely
+slow because DateTime.Parse is very slow.  That's why we don't do that
+(automatically).  Also since Sqlite doesn't store DATETIMEs natively
+in any special format besides as a string, it makes some sense to me
+that the client user should specify how he wants the DateTime encoded
+in the DB.
+
+It's not an ideal situation, but I'm marking this as not a bug.