dotConnect for Oracle has some options that customize translating LINQ to Entities to SQL statements. The list of these options includes:

• NoEscapeLike - allows disabling ESCAPE in LIKE expression. The default value is false.
• CaseInsensitiveLike - allows using case insensitive comparison mode, when translating LINQ to Entities extension methods .Contains(), .EndsWith(), .StartsWith(). The default value is false.
• CaseInsensitiveComparison - allows using case insensitive comparison mode, when translating LINQ to Entities extension method .Equals(). The default value is false.

• OrderByNullBehavior. Determines how NULL values will participate in sorting (whether to add NULLS FIRST or NULLS LAST to the ORDER BY clause of generated SQL queries). This option can have the following values:

  • Default. In this case neither NULLS FIRST nor NULLS LAST is added to the generated ORDER BY clauses.

  • NullsFirst . In this case NULLS FIRST is added to the generated ORDER BY clauses.

  • NullsLast. In this case NULLS LAST is added to the generated ORDER BY clauses.
• AdvancedMetadataQuery - Allows you to turn on the advanced metadata query mode. When set to true, the provider behaves similarly to the Visual Studio Entity Data Model Wizard when querying metadata. This mode should be used when the functionality of System.Data.Entity.Design.dll is used for metadata retrieving in the project. The default value is false.

• TrueValueNumber - Allows you to specify which number values are accepted as a true boolean value:

  • One. Only value of 1 is accepted as as a true boolean value.

  • NotZero . Any non-zero number is accepted as a true boolean value. This is the default value.

• UseCSharpNullComparisonBehavior - allows performing NULL checks when comparing a property (column) with a value (parameter) in LINQ to Entities. The default value is false.

Please note that the last two options work with both common DefaultValue SSDL attribute and the new custom devart:DefaultValue SSDL attribute. The latter attribute does not trigger the type consistency check, so you can use a wider range of default values, like CURRENT_TIMESTAMP or my_sequence.nextval.

Here is a simple example:

<Property Name="ProductID" Type="int" Nullable="false" 
devart:DefaultValue="my_sequence.NEXTVAL" StoreGeneratedPattern="Identity" />

The generated SQL command looks like the following:

INSERT INTO "Product"
  ("ProductID","ProductName","UnitScale","InStock","Price","DiscontinuedPrice")
  VALUES(my_sequence.NEXTVAL,:p0,:p1,:p2,:p3,:p4)

These options can be set either in code as the properties of the EntityProviderConfig.QueryOptions object or in the project config file as the attributes of the QueryOptions element of the Devart.Data.Oracle.Entity tag.