One of the most sophisticated issues with supporting Entity Framework is to accommodate the peculiarities of different DBMS, because Entity Framework is the easiest to use with Microsoft SQL Server. Some of the conflicts may be resolved with the following options, which can be set as the properties from the Workarounds class or in the config file as the attributes of the Workarounds element of the Devart.Data.SQLite.Entity tag.:

IgnoreSchemaName

Default value is false. When set to true, this property makes provider remove the schema (database) name from all commands and queries, no matter whether Schema is specified in the model or not. A command will use the schema from the connection.

This workaround is very useful in EF 4.1 Code First, since the "dbo" schema is set by default (like in SQL Server), and writing either attribute-based or fluent mapping is rather a time-consuming task. This functionality is useful in case of the Model or Database First approach as well. If the production and testing schemas have identical structure, it is enough to use this workaround, and no manual Schema replacing or removing is necessary in this case.

IgnoreDboSchemaName

Default value is true for Entity Framework 4.3 Code-First Migrations. When set to true, this property makes provider remove the "dbo" schema (database) name from all commands and queries. A command will use the schema from the connectio n.

Unlike the previous option, it allows you to explicitly specify a schema name other than "dbo" for tables.

DisableQuoting

Default value is false. This property allows the user to disable quoting all identifiers in all queries and commands.

The example code that disables quoting:

SQLiteEntityProviderConfig config = SQLiteEntityProviderConfig.Instance;  
config.Workarounds.DisableQuoting = true;  

Dim Config As SQLiteEntityProviderConfig
Config = SQLiteEntityProviderConfig.Instance
Config.Workarounds.DisableQuoting = True