[Mono-bugs] [Bug 78618][Nor] New - DateTime.Parse format exception with milliseconds

[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 atsushi at ximian.com.

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

--- shadow/78618	2006-06-13 13:02:13.000000000 -0400
+++ shadow/78618.tmp.13875	2006-06-13 13:02:13.000000000 -0400
@@ -0,0 +1,57 @@
+Bug#: 78618
+Product: Mono: Class Libraries
+Version: 1.1
+OS: GNU/Linux [Other]
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Normal
+Component: CORLIB
+AssignedTo: atsushi at ximian.com                            
+ReportedBy: dbrain at bandwidth.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: DateTime.Parse format exception with milliseconds
+
+Description of Problem:
+
+Using mono 1.1.13.4 there is a discrepancy between date parsing between
+mono and MS.
+
+e.g:
+
+DateTime.Parse("2006-05-05 5:55:55.555")
+
+Will parse under MS.Net but give a format exception under mono.
+
+Steps to reproduce the problem:
+
+Run code containing:
+DateTime date=DateTime.Parse("2006-05-05 5:55:55.555")
+
+Actual Results:
+
+Format exception
+
+Expected Results:
+
+'date' should now be a correct date object
+
+How often does this happen? 
+
+Always
+
+
+Additional Information:
+
+Appears to be related to milliseconds - remove, and DateTime.Parse works.
+
+Could be an issue for other users as this time format is the default for
+Ngpsql/Postgresql timestamp.
+
+------- Additional Comments From atsushi at ximian.com  2006-06-13 13:02 -------
+Any serious DateTime user should use ParseExact() instead. Parse()
+could fail depending on the culture.