Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose Metamodel getters in the SessionFactory APIS #2014

Open
DavideD opened this issue Nov 14, 2024 · 3 comments
Open

Expose Metamodel getters in the SessionFactory APIS #2014

DavideD opened this issue Nov 14, 2024 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@DavideD
Copy link
Member

DavideD commented Nov 14, 2024

From this conversation on Zulip:

you might want to look into exposing all metamodels directly in Reactive though. From what I can see only the JPA one is exposed right now, but not org.hibernate.metamodel.MappingMetamodel, which needs to be retrieved through hoops (see above)

@DavideD DavideD added the enhancement New feature or request label Nov 14, 2024
@DavideD DavideD added this to the 3.0.0.Alpha1 milestone Nov 14, 2024
@gavinking
Copy link
Member

Not sure what this issue is about, but if it's about exposing org.hibernate.metamodel.MappingMetamodel on an API, we should definitely not do that. MappingMetamodel exposes SPI-level types. Notice that SessionFactory in ORM does not expose this type.

@DavideD
Copy link
Member Author

DavideD commented Nov 14, 2024

Ok, something to look into

@gavinking
Copy link
Member

gavinking commented Nov 14, 2024

Note that it's already exposed via ReactiveSession.getFactory().getMappingMetamodel(). (Which is an SPI.)

@DavideD DavideD added problem A limitation or source of discomfort and removed problem A limitation or source of discomfort labels Dec 6, 2024
@DavideD DavideD modified the milestones: 3.0.0.Beta1, next Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants