Note that Entity has an Opinion called renameable which will be the value Fixed when a querySchema is specified.
That means that even if the NamingSchema is UpperCase, the resulting query will select t_person as opposed
to T_PERSON or Person.
Note that Entity has an Opinion called `renameable` which will be the value `Fixed` when a `querySchema` is specified.
That means that even if the `NamingSchema` is `UpperCase`, the resulting query will select `t_person` as opposed
to `T_PERSON` or `Person`.
Entities represent the actual tables/views being selected. Typically, something like:
comes from something like: When you define aquerySchema
, the fields you mention inside becomePropertyAlias
s. For example something like: Becomes something like: Note that Entity has an Opinion calledrenameable
which will be the valueFixed
when aquerySchema
is specified. That means that even if theNamingSchema
isUpperCase
, the resulting query will selectt_person
as opposed toT_PERSON
orPerson
.
When you define a `querySchema`, the fields you mention inside become `PropertyAlias`s. For example something like: Becomes something like: Note that Entity has an Opinion called `renameable` which will be the value `Fixed` when a `querySchema` is specified. That means that even if the `NamingSchema` is `UpperCase`, the resulting query will select `t_person` as opposed to `T_PERSON` or `Person`.SELECT p.name FROM People p
something like: