StoreGeneratedPattern attribute in SSDL from Entity Designer

StoreGeneratedPattern attribute in SSDL from Entity Designer by Fabio Vassura

Closed

as External Help for as External

Type:	Bug
ID:	774005
Opened:	12/11/2012 2:11:25 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Hi, we have the same problem described in KB2561001 with a new MVC 4 project using VS2012, EF 5 and ODP.NET for Oracle 11.

Everytime we "generate database from model", the ssdl part on edmx file loses the "storedGeneratedPatter=Identity" attribute.

Are you planning an hotfix for VS2012 and EF 5 supporting Oracle too?

Details (expand)

Visual Studio 2012

Create a new entity in EF Model Designer with a PK column using "StoredGeneratedPattern=Identity" attribute.
Generate database from model.

English

Windows 7 SP1

Italian

If you look at the mapped column properties, StoredGeneratedPattern attribute is set to "None"

The SSDL part on EDMX file should mantain StoredGeneratedPattern attribute value,
instead it is losing it

0 attachments

I can repro the problem but only on Oracle. The long and the short of it is it’s a problem with the Oracle provider.

Details

If you set things up the way you’re supposed to on Oracle (see e.g. the Model First part of this page http://download.oracle.com/oll/obe/EntityFrameworkOBE/EntityFrameworkOBE.htm) then you set Database Generation Workflow as “Generate Oracle Via T4 (TPT)” and DDL Generation Template as “SSDLToOracle.tt (VS)”. If you have these set and do Model First then I can repro the the problem.

The “Generate Oracle Via T4 (TPT).xaml” is in $(VisualStudio)\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\DBGen. It specifies a class “Oracle.VSDevTools.OracleVSGTPT_CsdlToSsdlActivity” in assembly Oracle.VSDevTools. It is this class which is responsible for generating the SSDL from the CSDL. This seems to be broken in that it is not generating the SSDL SGP attribute. (There is a similar class for TPH – and that seems to be broken too).

Workarounds : None

If, even though the connection is for Oracle, you set Database Generation Workflow as the default “TablePerTypeStrategy.xaml” and DDL Generation Template as the default “SSDLToSQL10.tt (VS)” then SGP generation works OK but you lose more important stuff about the types / precision etc of the SSDL properties and you are generating DDL for SQL Server.

If you have already generated the SSDL you can, even with Database Generation Workflow = “Generate Oracle Via T4 (TPT)” and change the SGP directly on the C-side property using the Properties Window. This will change the SGP on the S-side property to match, but the moment you do “Generate DB from Model” the S-side SGP attribute will disappear again.

We are forwarding the issue on to Oracle to see if they can update the class.