Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
hibernate-orm/design/type-system-domain.adoc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

54 lines
1.6 KiB
Plaintext
Raw Permalink Normal View History

6 - SQM based on JPA type system - Continued work on mapping model and conversion from SQM to SQL. Currently flushing out mapping model - how expressive do we want this to be? Do we really want to re-use the walking contracts? Or create a new SPI/impls based on MappingModelExpressable?
2019-08-15 20:24:16 -04:00
= Domain type system (JPA/SQM)
The JPA type system is an "unmapped" model, meaning that it has no mapping information -
no references to tables, columns, etc. The base contract for Hibernate's extension to the
JPA model is `org.hibernate.metamodel.model.domain.DomainType`.
Hibernate's Semantic Query Model (SQM) is defined in terms of these JPA type extensions,
expressable -> expressible everywhere
2022-01-23 10:32:43 -05:00
through the `SqmExpressible` contract, allowing parts of the application's
6 - SQM based on JPA type system - Continued work on mapping model and conversion from SQM to SQL. Currently flushing out mapping model - how expressive do we want this to be? Do we really want to re-use the walking contracts? Or create a new SPI/impls based on MappingModelExpressable?
2019-08-15 20:24:16 -04:00
domain model to be used as part of an SQM tree.
[plantuml,SqmTypeSystem,png]
design doc work
2020-08-25 21:17:35 -04:00
.Domain type system
6 - SQM based on JPA type system - Continued work on mapping model and conversion from SQM to SQL. Currently flushing out mapping model - how expressive do we want this to be? Do we really want to re-use the walking contracts? Or create a new SPI/impls based on MappingModelExpressable?
2019-08-15 20:24:16 -04:00
....
@startuml
skinparam handwritten true
interface DomainType
interface SimpleDomainType
interface BasicDomainType
interface AnyMappingDomainType
interface ManagedDomainType
interface EmbeddableDomainType
interface IdentifiableDomainType
interface EntityDomainType
interface MappedSuperclassDomainType
expressable -> expressible everywhere
2022-01-23 10:32:43 -05:00
interface SqmExpressible
6 - SQM based on JPA type system - Continued work on mapping model and conversion from SQM to SQL. Currently flushing out mapping model - how expressive do we want this to be? Do we really want to re-use the walking contracts? Or create a new SPI/impls based on MappingModelExpressable?
2019-08-15 20:24:16 -04:00
interface SqmPathSource
interface PersistentAttribute
interface SingularPersistentAttribute
interface PluralPersistentAttribute
DomainType <|-- SimpleDomainType
SimpleDomainType <|-- BasicDomainType
SimpleDomainType <|-- AnyMappingDomainType
SimpleDomainType <|-- ManagedDomainType
ManagedDomainType <|-- EmbeddableDomainType
ManagedDomainType <|-- IdentifiableDomainType
IdentifiableDomainType <|-- MappedSuperclassDomainType
IdentifiableDomainType <|-- EntityDomainType
expressable -> expressible everywhere
2022-01-23 10:32:43 -05:00
SqmExpressible <|-- DomainType
SqmExpressible <|-- SqmPathSource
6 - SQM based on JPA type system - Continued work on mapping model and conversion from SQM to SQL. Currently flushing out mapping model - how expressive do we want this to be? Do we really want to re-use the walking contracts? Or create a new SPI/impls based on MappingModelExpressable?
2019-08-15 20:24:16 -04:00
SqmPathSource <|-- EntityDomainType
SqmPathSource <|-- PersistentAttribute
PersistentAttribute <|-- SingularPersistentAttribute
PersistentAttribute <|-- PluralPersistentAttribute
@enduml
....