Steve, I still need to look at the wiki page and will give more detailed feedback on some parts of it.
One general thing coming to mind though is how support for OGM could be improved. On first thought I'd say the "Java side" of Type might stay as is, but the "SQL side" (or "datastore side") and read/write logic interacting with result sets etc. would have to look differently in the case of OGM. If this part of the story could be made pluggable somehow, than a custom factory of sorts in OGM could plug in its dedicated implementation of the "datastore side". Not sure how it'd look in practice, the implementations would be rather different (we don't work with ResultSet at all in OGM), so I suppose it might require casting to the expected subtype when working with Type in ORM or OGM. Currently, we completely override the Type hierarchy from ORM with a corresponding GridType hierarchy in OGM, but it might be possible to re-use many more code by just customizing the "datastore side". Plus, it'd be a tad more efficient for OGM, as we can skip the translation from Type to GridType. I might provide some more details once having studied the current proposal in more depth, just wanted to get out these thoughts to you. --Gunnar 2016-06-22 18:54 GMT+02:00 Steve Ebersole <st...@hibernate.org>: > I started a wiki discussing the proposal for the type system redesign. > Let's get discussions about it starter sooner rather than later. Thanks! > > https://github.com/hibernate/hibernate-orm/wiki/6.0---Type-redesign > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
