Page 1 of 1

Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)

Posted: Fri 10 Mar 2017 16:42
by BGrojer
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.

Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)

Posted: Wed 15 Mar 2017 10:48
by Shalex
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)

Posted: Mon 27 Mar 2017 08:20
by 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).
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)

Posted: Tue 28 Mar 2017 11:22
by Shalex
BGrojer wrote:I can confirm there is NO issue with that scenario.
Thank you for confirming.
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.
Please send us a small test project for reproducing the issue.

Re: Mapping of Complex Type ignored settings in CodeFirst (EF 6.x)

Posted: Tue 18 Apr 2017 05:11
by bharaniKumar
[quote="
Shalex wrote:
BGrojer wrote:I can confirm there is NO issue with that scenario.
Thank you for confirming.
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.
Please send us a small test project for reproducing the issue.
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).
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)

Posted: Tue 18 Apr 2017 14:23
by Shalex
bharaniKumar, please send us a small test project for reproducing the issue.