[Mono-bugs] [Bug 417398] New: System.Data.DataRowComparer.Default doesn' t compare by row contents
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu Aug 14 13:06:43 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=417398
Summary: System.Data.DataRowComparer.Default doesn't compare by
row contents
Product: Mono: Runtime
Version: 2.0
Platform: i386
OS/Version: Windows Server 2003
Status: NEW
Severity: Major
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: jpjerkins at yahoo.com
QAContact: mono-bugs at lists.ximian.com
Found By: Community User
I'm reading through Pro LINQ by Joseph C. Rattz when I find-out that the Mono
2.0 preview is out, and that it supports (among other things) Linq to Datasets,
which is what I'm reading about. So I entered a simple example from p346.
It demonstrates the difference between using IEnumerable<T>.Except with and
without the DataRowComparer.Default. Without it no two DataRows ever match,
even with the same data, since the runtime does reference comparison. The
DataRowComparer is supposed to dive into the DataRows' data and compare actual
values.
The example compiles fine with gmcs. But - on a gmcs-compiled EXE - the
Microsoft runtime shows correct results (duplicate rows removed when using
DataRowComparer), while the mono runtime shows the same results whether using
DataRowComparer or not. Literally, typing "Sample.exe" at the command-prompt
shows the right results, but typing "mono Sample.exe" shows wrong results.
This is my first bug report, and I'm actually willing to fix it. But I'd need
info on how to contribute. My usual environment is either a Mac or Windows,
though I can get Ubuntu running in a VM pretty quickly if need be.
--
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.
More information about the mono-bugs
mailing list