Bug #89772 Entity Framework Core string fields being created as NOT NULL
Submitted: 22 Feb 2018 15:08 Modified: 23 Mar 2018 12:29
Reporter: Richard Collette Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S1 (Critical)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[22 Feb 2018 15:08] Richard Collette 
Description:
As per the Entity Framework documentation, nullable types such as string should default to being optional. 

Instead I am finding that string fields at least in some cases are being created as NOT NULL columns.  The field does not have any index or other restrictions.

I have noticed that owned/embedded entities do not exhibit this problem.

I have had to switch to Pomelo driver because this is a blocker for my project.  Hence I have marked this critical since it prevents me from using Connector Net at all.

How to repeat:
Unfortunately, I do not have time at the moment to create a specific subset of code to demonstrate this.
[23 Feb 2018 12:29] Chiranjeevi Battula 
Hello Richard Collette,

Thank you for the bug report.
Could you please provide repeatable steps (exact steps/sample project, C/Net,MySQl version, full stack trace etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.
[24 Mar 2018 1:00] Bugs System 
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".