The most severe showstopper concerns the generation of a database structure or the corresponding script. Consider the following SSDL type definition:
Code: Select all
<EntityType Name="InvoiceLines">
<Key>
<PropertyRef Name="InvoiceId" />
<PropertyRef Name="LineId" />
</Key>
<Property Name="InvoiceId" Type="int" Nullable="false" />
<Property Name="LineId" Type="int" Nullable="false" StoreGeneratedPattern="Identity" />
</EntityType>
In this case, the attribute StoreGeneratedPattern="Identity" has no effect when generating a corresponding table/script: neither GENERATED ALWAYS AS IDENTITY (Oracle 12) nor a sequence + trigger pair (Oracle 11) is generated for this type - either in runtime using CreateDatabase/Script() or in design-time using Devart T4 transform:
Code: Select all
CREATE TABLE "InvoiceLines" (
"InvoiceId" NUMBER(10) NOT NULL,
"LineId" NUMBER(10) NOT NULL,
PRIMARY KEY ("InvoiceId", "LineId")
)
Please confirm that it is a bug in dotConnect for Oracle and provide some estimation if it can (and is going to be) fixed in the coming releases. Your answer will help us making a decision about adopting your provider for our product.