Bug #44986 binary(16) and tinyint(1) is not converted using ADO .NET Data Entities
Submitted: 20 May 16:27 Modified: 23 Jun 18:48
Reporter: Morten Andersen
Status: Need Doc Info
Category:Connector/Net Severity:S2 (Serious)
Version:6.0.3 OS:Microsoft Windows (Vista 32)
Assigned to: Target Version:
Tags: Guid, ADO

[20 May 16:27] Morten Andersen 
Description:
If I use the connector to create a DataTable for me, the binary(16) is converted into a
Guid. Using the ADO.NET Data Entities designer you do not get this behavior. I guess this
is the case for all data types.

How to repeat:
1. Create a entity from a table that contains a binary(16) column
2. Look at the data type for that column. You will now see an unexpected data type
(Byte[])
[21 May 17:53] Reggie Burnett 
tinyint(1) has already been fixed.  We are fixing the guid issue now.  We will be changing
from binary(16) to binary(36) so that users can use the sql function UUID() to populate
those columns.  We will maintain binary(16) support using a connection string option that
we will eventually deprecate.
[22 May 23:58] Reggie Burnett 
tinyint(1) has been fixed but binary(16) has not.  Marking as verified
[26 May 21:45] Bugs System 
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/74980
[26 May 21:46] Reggie Burnett 
fixed in 6.0.4