[hibernate-dev] Is SQM going to remain a separate component?

[Steve Ebersole]

On Fri, May 27, 2016, 3:01 AM Gunnar Morling <gunnar at hibernate.org> wrote:

>
> This looks awesome and we look forward to make use of it in Hibernate OGM.
> One thing I'm wondering is how closely tied to Hibernate ORM 6 this will
> be. Is the plan to move all the SQM bits into the hibernate-orm repo
> eventually? Or will SQM remain a separate component, and only the
> implementation of the type system will live in ORM?
>

The plan is to have it remain a separate artifact.

That was done to allow OGM (send others) to more easily consume SQM, mainly
because of the type system abstraction.


> The reason for asking is that I'm trying to gauge how feasible it'd be to
> use SQM in a Hibernate OGM based on ORM 5.x. That'd be much simpler (or
> even only actually doable without essentially copying code), if SQM would
> remain separate, and we'd "only" have to copy/backport the type system
> implementation.
>

This would be *possible*.  Not sure how good of an idea it is, but that's a
different discussion :)