MySQL Bugs: #86043: Can't use BigInt or Double as userId instead of Int32 (default)

Bug #86043	Can't use BigInt or Double as userId instead of Int32 (default)
Submitted:	22 Apr 2017 2:23	Modified:	29 Sep 18:07
Reporter:	Sachin Erande	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	6.8.8	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	MySqlMembershipProvider

Description:
MySql.Web.Security.MySQLMembershipProvider.GetUserId   --> Method always returns Int32. 
This method is invoked internally by ValidateUser and CreateUser Methods. 
If we use BIGINT or higher size data type for column "userId" in tables "my_aspnet_users","my_aspnet_membership". 
Above type cast error occurs. 
Please let this bug be fixed as early as possible. 

I can't use large size primary key for userId. 
Thank you.

How to repeat:
modify column userId of tables "my_aspnet_users","my_aspnet_membership" to BIGINT or double.
Try to perform login or register using the methods on mysqlmembershipprovider
ValidateUser
CreateUser 

TypeCast error occurs because private method "GetUserId" always returns int32 however implicitely it is supposed to be generic according to the datatype of column in database.
This indicates mysql only supports int columns.
please fix this asap. I am stuck.

Suggested fix:
TypeCast error occurs because private method "GetUserId" always returns int32 however implicitely it is supposed to be generic according to the datatype of column in database.
This indicates mysql only supports int columns.
please fix this asap. I am stuck.

Exception screenshot from visual studio

Attachment: mysql_userId_BigInt.png (image/png, text), 33.66 KiB.

Verufued, Treating as a feature request since current behavior is as per design.