Bug 14903 - OdbcCommandBuilder generates wrong parameters for it's where clause
Summary: OdbcCommandBuilder generates wrong parameters for it's where clause
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Data ()
Version: master
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-09-21 13:30 UTC by wdehoog
Modified: 2013-09-21 13:30 UTC (History)
1 user (show)

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 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description wdehoog 2013-09-21 13:30:02 UTC
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.