When mapping a complex type Property in the latest Version the "ColumnName" is ignored during database creation.
e.g. the mapping
Property(p => p.MyComplexType.MyPropertyId).HasColumnName("MyId").IsRequired();
does not result in a column with name "MyId" in the table instead it creates a tablename MyComplexType_MyPropertyId. During query the "MyId" is used.
The standard Sql Server implementation creates it correctly.
Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
We have sent a test project to your email. Please modify it for reproducing the issue and send the updated project to us.
Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
Thanks for your helps guys. I can confirm there is NO issue with that scenario. (the issue was a derived class that was mapped automatically by EntityFramework (and a missing configuration).
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
Thanks for your support.
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
Thanks for your support.
Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
Thank you for confirming.BGrojer wrote:I can confirm there is NO issue with that scenario.
Please send us a small test project for reproducing the issue.BGrojer wrote:the issue was a derived class that was mapped automatically by EntityFramework (and a missing configuration).
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
-
- Posts: 9
- Joined: Tue 07 Mar 2017 13:40
Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
[quote="
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
Thanks for your support.[/quote]
I have facing same problem........
BGrojer"]Thanks for your helps guys. I can confirm there is NO issue with that scenario. (the issue was a derived class that was mapped automatically by EntityFramework (and a missing configuration).Shalex wrote:Thank you for confirming.BGrojer wrote:I can confirm there is NO issue with that scenario.
Please send us a small test project for reproducing the issue.BGrojer wrote:the issue was a derived class that was mapped automatically by EntityFramework (and a missing configuration).
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
The automatically mapped configuration leaded to issues in Oracle but not SQL Server.
Thanks for your support.[/quote]
I have facing same problem........
Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)
bharaniKumar, please send us a small test project for reproducing the issue.