[Mono-bugs] [Bug 663914] New: DataTable XmlDeserialization DBNull handling error on ValueType column

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=663914

https://bugzilla.novell.com/show_bug.cgi?id=663914#c0


           Summary: DataTable XmlDeserialization DBNull handling error on
                    ValueType column
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: i386
        OS/Version: RHEL 5
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Sys.Data
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: rg at njl.hu
         QAContact: mono-bugs at lists.ximian.com
          Found By: Community User
           Blocker: ---


Created an attachment (id=407970)
 --> (http://bugzilla.novell.com/attachment.cgi?id=407970)
test program and patch

Description of Problem:

When a DataTable or DataSet has a row with Current and Original version and an
integer column's original value is DBNull, after deserialization the original
version of the row contains 0 in the integer column. This causes the
DBDataAdapter.Update fail with a DBConcurrencyException. This also happens when
calling a SOAP webservice and passing a DataTable or DataSet as argument with
the above content.

Steps to reproduce the problem:
1. Compile attached Nulltest.cs with "gmcs -r:System.Data.dll Nulltest.cs"
2. Run program with "mono Nulltest.exe"


Actual Results:
Original i:
Original i:0

Expected Results:
Original i:
Original i:


How often does this happen? 
Every time

Additional Information:
I've made a patch to DataRow.cs, it's quite simple and solve's the problem.
Please check weather it's correct and submit to the repository.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.