-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Should we support flattening object embedding? If yes, how should it be configured? Which of the ways Hibernate ORM has for configuring object embeddings should we support?
- See https://mongodb.slack.com/archives/C07EUDEQ70X/p1738996492125489 for more details and the discussion.
- See com.mongodb.hibernate.BasicInsertionTests.BookWithEmbeddedField, com.mongodb.hibernate.BasicInsertionTests.Author.
Update:
- We decided not to support @Embedded @JdbcTypeCode(SqlTypes.JSON), @Embedded @JdbcTypeCode(SqlTypes.SQLXML). Should we explicitly throw when these annotations are used? We should also investigate whether we can change the behavior of these annotations, because if we can, we may use @Embedded @JdbcTypeCode(SqlTypes.JSON) instead of @Embedded @Struct as the former may be more appropriate.
- After doing more research, nathan.xu@mongodb.com said that changing the existing Hibernate ORM behavior does not seem to be possible (we should double check this). So we technically have only two options: leave the behavior of just @Embedded as is, or forbid using just @Embedded by explicitly throwing.
- related to
-
HIBERNATE-59 Embedding simple BsonDocument
-
- In Progress
-