ORM logging configuration using
Two logging "sources" are defined in this section.
osamesOrmDetailedTraceSource(log with stack trace).
When logging sources are missing, logging will occur to default logger of
Definition of ADO.NET providers available to application
Providers should be defined in system.data section, like in sample code below. Else ORM will not be able to detect them on the machine.
A single provider can be active at time at ORM level. Several ones can be declared as usable on the machine.
AppSettings and ConnectionString sections description
Following keys are required :
|Relative path||Application root relative path of folder containing XML configuration files : templates and mapping||\\\Config\|
|Relative path||Application root relative path of folder containing XSD files to validate configuration XML files||Config\xml_schemas|
|File name||XSD file to validate XML templates file||sqlTemplates.xsd|
|File name||XSD file to validate XML mapping file||omo-mapping.xsd|
|File name||XML templates file||sqltemplates.xml|
|File name||XML mapping file||omo-mapping.xml|
Name of active connection. Identical to one of
|Number from 0 to 2|
Contextual error handling mode before throwing the exception:
Option removed in version 0.3, cf ORM-173 - Getting issue details... STATUS
Definition of every usable connection string, as triplets:
name: connection name as defined in
connectionString: connection string value, see example: Connexion String
providerName: invariant name of ADO.NET provider (cf