Ok, so it looks as though there is a problem with the System.Data.Odbc
library... a pretty major and glaring problem that I can't believe was even
allowed to be checked into the repository.
Here is the code for the GetSchema calls:
public override DataTable GetSchema ()
{
if (State == ConnectionState.Closed)
throw ExceptionHelper.ConnectionClosed ();
return MetaDataCollections.Instance;
}
public override DataTable GetSchema (string collectionName)
{
return GetSchema (collectionName, null);
}
public override DataTable GetSchema (string collectionName,
string []
restrictionValues)
{
if (State == ConnectionState.Closed)
throw ExceptionHelper.ConnectionClosed ();
return GetSchema (collectionName, null);
}
Seems pretty obvious to me that GetSchema(string, string[]) is designed
specifically to blow up memory until the VM decides to stop it. It would
have been more useful if it just threw a not implemented exception and not
actually pretend to do something... It would have been even more useful if
any of the resources associated with this library would have even indicated
in the slightest that these functions not only do nothing, they actually
kill your call stack. Maybe they were testing the StackOverflowException?
Does anyone know how to go about fixing this? Is there any way to either
contribute to the project, or contact someone who is contributing? Also,
does anyone know how to find the dev that checked in this crap so I can
punch him in the throat? :)
--
View this message in context:
http://mono.1490590.n4.nabble.com/ODBC-GetSchema-failing-tp4665832p4665833.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
