MySQL Bugs: #51837: AllowDBNull and DefaultValue on DataColumn are never correct

Bug #51837	AllowDBNull and DefaultValue on DataColumn are never correct
Submitted:	8 Mar 2010 16:41	Modified:	10 Apr 2010 15:00
Reporter:	Israel DiPeri	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.0	OS:	Windows (XP)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Whenever I execute a query and try to look at the AllowDBNull and DefaultValue properties of the DataColumn they are always true and an empty object, respectively.
The table definition that I'm querying definately has a mix of columns that allow or don't allow null and at least once column has a default value yet this information has never been reflected in the returned results.

How to repeat:
Create a table with at least 1 column that allows null and 1 column that doesn't and at least 1 column that has a default value.

Then execute this C# code:

MySqlDataAdapter adapter = new MySqlDataAdapter( "select * from MyTable;", connection);
DataSet dataset = new DataSet("TableData");
adapter.Fill(dataset);

foreach(DataColumn col in dataset.Tables[0].Columns)
{
   string defaultValue = col.DefaultValue.ToString();
   bool allowDBNull = col.AllowDBNull;
}

Observer that defaultValue is always "" and allowDBNull is always true

Do you use Connector/Net 5.1.4? What exact version of MySQL server are you working with?

I'm using the .NET connector version 5.1.4.0 with MySQL version 5.0 - I'm not sure if there's more detailed version info somewhere but the exe etc have no version information 5.0 is as much as I can get from it.

Israel, Valeriy, I believe there is a similar report already in BugsDB. Will take it from here.

Israel, we no longer support c/NET 5.x, please use our newer drivers and retest.

According to Rev 181:
Added checks on each type safe datareader method to keep them from working on null
columns. You should use .IsDbNull to check for null.

This could be, at least in part, a duplicate of Bug#49936.

Tonci,
From what I read Bug#49936 doesn't seem like a duplicate of this issue.  I don't have an issue with specific values being null I have issues when I check the schema and want to know if a field is nullable (or has a default).  I need to know that for another piece of code which tried to automatically generate some SQL for the table and I need to know if I can set a value to null or if I have to do something else.
I'm not sure what you mean by "no longer support c/NET 5.x" do you mean the .NET connection ver 5.1.4.0 is no longer supported?  Note I mistakenly said the version of MySQL was 5.1.4.0 but I really meant to say it was 5.0.

I mistakenly said the MySQL version was 5.1.4.0 but I really mean that the .NET connector was 5.1.4.0 and MySQL was version 5.0

Israel, thanks for info added. Unfortunately, we do not support c/NET 5.x any more so please try repeating with newer versions.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".