DbOom
instance (who would guess :). You will have one instance per database. DbOom
recognizes the single-database usage, making available various shortcuts; mainly preventing you to carry on the instance of DbOom
.DbOom
offers fluent builder to construct itself.DbOom
detects the database vendor and applies some default naming convention.DbOom
provides access to following components:DbOomConfig
- configuration, mainly naming conventions,DbQueryConfig
- query-related configuration,DbEntityManager
- manager of entity mappings,DbSessionProvider
- session provider,ConnectionProvider
- connection providerQueryMap
- map of named queries.DbOom
also is a factory for all DbOom working tools:entities()
- returns DbEntitySql
factory,sql()
- creates new DbSqlBuilder
,query()
- creates new DbOomQuery()
.DbOom
. {: .attn}DbOom
. Once when created, the instance of DbOom
can be accessed using the following:get()
method will throw exception if multiple databases are in use, or none.DbOom
as an argument. In single-database mode, you can use static constructor methods, that does not take DbOom
instance. For example, this usage:DbOom
instance directly instead, no matter which mode is in use: