Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 14903 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
OdbcCommandBuilder generates special parameters for columns who allow NULL. However these are named the same as the columns which will result in type errors when binding the parameters.
It looks like the first parameter (named nullParam) created in CreateOptWhereClause needs always to be created with sourcecolumn being empty. If I do so no errors occur anymore and the query is ok.
As of why this works I guess this has to do with the way parameters are looked up in the parameter collection.