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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80361 --- shadow/80361 2007-01-04 16:54:10.000000000 -0500 +++ shadow/80361.tmp.783 2007-01-04 17:27:28.000000000 -0500 @@ -43,6 +43,17 @@ handling bug. ------- Additional Comments From [EMAIL PROTECTED] 2007-01-04 16:54 ------- updated the summary. the bug is that we aren't doing anything with the exception that's raised by System.Data when you attempt to set the column field to whatever the db null value is. + +------- Additional Comments From [EMAIL PROTECTED] 2007-01-04 17:27 ------- +I don't think it's only related to AllowDBNull handling (although +you're right in saying that nothing is done with the Exception from +System.Data). I also get the problem when AllowDBNull is set to true. + +I think there another issue: DataGridTextBox.IsInEditOrNavigateMode is +true after pressing CTRL+0 (and if no other key was pressed), and as +as such the updated value is ignored (in DataGridTextBoxColumn.Commit). + +So there appear to be two issues here. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
