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-mapping.adoc

72 lines
2.0 KiB
Plaintext
Raw 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
= Mapping model
design doc work
2020-08-25 21:17:35 -04:00
The mapping model encompasses the complete mapping of objects to/from database. It is the
model used to drive read and write operations.
[NOTE]
----
As of 6.0, only read operations are implemented to use this mapping model. Future versions will hopefully
move writing to use this mapping model as well
----
[plantuml,MasppingTypeSystem,png]
.Mapping type model (org.hibernate.metamodel.mapping)
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 MappingType
design doc work
2020-08-25 21:17:35 -04:00
interface ManagedMappingType
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
design doc work
2020-08-25 21:17:35 -04:00
interface MappingModelExpressable
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 ValueMapping
interface BasicType
interface ModelPart
interface ModelPartContainer
design doc work
2020-08-25 21:17:35 -04:00
MappingType <|-- BasicType
MappingType <|-- JdbcMapping
MappingType <|-- ManagedMappingType
MappingType <|-- CollectionMappingType
ManagedMappingType <|-- EmbeddableMappingType
ManagedMappingType <|-- EntityMappingType
MappingModelExpressable <|-- ValueMapping
MappingModelExpressable <|-- ModelPart
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
ValueMapping <|-- BasicType
design doc work
2020-08-25 21:17:35 -04:00
ModelPart <|-- BasicValuedModelPart
ModelPart <|-- EmbeddableValuedModelPart
ModelPart <|-- EntityValuedModelPart
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
ModelPart <|-- AttributeMapping
ModelPart <|-- EntityIdentifierMapping
ModelPart <|-- EntityVersionMapping
ModelPart <|-- EntityDiscriminatorMapping
design doc work
2020-08-25 21:17:35 -04:00
ModelPart <|-- CollectionPart
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
design doc work
2020-08-25 21:17:35 -04:00
ModelPartContainer <|-- EntityMappingType
ModelPartContainer <|-- EmbeddableMappingType
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
@enduml
....
== Relationship with legacy "persister walking" SPI
`org.hibernate.metamodel.model.mapping` contract corollaries in `org.hibernate.persister.walking`:
EntityMapping::EntityDefinition
EmbeddableMapping::CompositionDefinition
AttributeMapping::AttributeDefinition
EntityIdentifierMapping::EntityIdentifierDefinition
== AllowableParameterType
HHH-15017 - Clean-up Query#setParameter overloads - https://hibernate.atlassian.net/browse/HHH-15017
2022-01-10 13:25:08 -05:00
`BindableType` is a contract that defines types that are valid for parameter binding in terms of an SQM query.
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
AT some point this needs to be "resolved" to a ValueMapping/Type/Bindable when generating the SQL AST and executing.
HHH-15017 - Clean-up Query#setParameter overloads - https://hibernate.atlassian.net/browse/HHH-15017
2022-01-10 13:25:08 -05:00
One option is to have the `BindableType` be resolved first to a `SqmExpressable`
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
`SqmExpressableAllowableParameterType#resolveSqmExpressable`