dotConnect for Oracle allows configuring creating and deleting database objects in the CreateDatabase() and DeleteDatabase() methods. These customizations are rather useful for the Code First approach. You can tweak the behaviour of the methods using the OracleEntityProviderConfig.DatabaseScript.Schema, OracleEntityProviderConfig.DatabaseScript.Table, OracleEntityProviderConfig.DatabaseScript.Column, OracleEntityProviderConfig.DatabaseScript.Index, and OracleEntityProviderConfig.DatabaseScript.ForeignKey classes.
DeleteDatabaseBehaviour. This enumeration determines the behavior of the DeleteDatabase() function.
Schema - entire schema, containing model objects, is created/deleted. If the model contains objects from other schemas, these schemas will be created/deleted as well.
Note: There is no possibility to delete the user that is currently connected in Oracle. Thus, to call the DeleteDatabase() method, the user must have grants to delete users and must not have any database objects that model objects are mapped to.
Tablespace - sets the name of the tablespace for the created tables.
NumericIdentityBehavior. This property manages generation of columns with StoreGenerationPattern="Identity". This property can have the following values:
MaxStringSize. This property determines a default size of the VARCHAR2 and NVARCHAR2 columns for Oracle 12c if it was not set explicitly in the Code-First CreateDatabase()/Code-First Migrations functionality. This property can have the following values:
Tablespace - sets the name of the tablespace for the created indexes.