Bug 29557 - System.Data.SqlClient GetSchema(string) throws exception
Summary: System.Data.SqlClient GetSchema(string) throws exception
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Data ()
Version: 3.12.0
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-04-29 17:18 UTC by Ryan
Modified: 2017-09-01 09:29 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Ryan 2015-04-29 17:18:32 UTC
This is related to bug 26140 in that the exception thrown is due to recent changes to DataTable "SourceTable is
required to be a non-empty string" is thrown on any call to GetSchema(string) from System.Data.SqlServer.  If a change to fix DataTable is a long way off, this should be an easier/quicker fix.
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2015-08-25 22:45:38 UTC
The particular change in behavior that appeared in Mono 4.0 leading to the "SourceTable is required to be a non-empty string" should hopefully be resolved as of Mono 4.0.3 (detached/429313d). I can verify that a simple test case that does fail with that message in earlier versions of Mono 4.0 now runs _without_ error in Mono 4.0.3.

The change in behavior was reverted in [1].

[1] https://github.com/mono/mono/commit/8d29aafd1c6d6e4edd5b2dd99411b97bc9ce8ea8


I will accordingly mark this bug as RESOLVED FIXED. If any users identify additional test cases that have changed behavior between Mono 3.12 and Mono 4.0 and are _not_ yet fixed in the latest builds of Mono, do of course feel free to file new additional bug reports.

If the original reporter of this bug (Ryan) finds that the specific problem from his original test case does not appear to be fixed, he can feel free to REOPEN the bug with additional details about the test case that still fails for him (ideally a few runnable lines of code, with the SQL server connection string optionally omitted).


Best,
Brendan
Xamarin Customer Support