Bug #37350 Using unsigned integers with autoincrement

Description:
In 'MySqlDataAdapter Class' doc, there is a note half way down:
'Note: Please be aware that the DataColumn class in .NET 1.0 and 1.1 does not allow columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns. If you plan to use autoincremement columns with MySQL, you should consider using signed integer columns.'

This (at least to me) indicates that this might have been/is fixed in .net 2.0 and later.
However, this is NOT the case even in .net 3.5 !

I found his page from MS, help for .net 3.5:
http://msdn.microsoft.com/en-us/library/229sz0y5.aspx
Find the note half down:
"... whereas a DataColumn only allows Int16, Int32, and Int64 to have the AutoIncrement property set."

How to repeat:
Read the doc

Suggested fix:
Remove the versions from the text, like this:

'Note: Please be aware that the DataColumn class in .NET does not allow columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns. If you plan to use autoincremement columns with MySQL, you should consider using signed integer columns.'

Now, not even I will get my hopes up.

Hi Poul and thanks for your report. Verified as described. MC, please update docs to reflect this.

Upon second thought, I actually think it's even better to say, like the MS doc:

"...only allows Int16, Int32, and Int64 ..."

This excludes other types like TinyInt, too.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/48019

Fixed in 5.1.7 and higher.  Online docs still need to be updated

Fixed main docs and added entry to 5.1.7 changelog:

Documentation incorrectly stated that “the DataColumn class in .NET 1.0 and 1.1 does not allow columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns”.