I'm not so sure a single "extras" artifact/module makes the most sense
though. Since some involve pulling in driver jars - I think (if we do
this) we ought to have `hibernate-extras-base` as well as db-specific
extensions (`hibernate-extras-pgsql`, ...).
We had a similar discussion recently on HipChat or mailing list (can't
remember which exactly)
On Thu, Sep 28, 2017 at 6:43 AM Sanne Grinovero <sanne(a)hibernate.org> wrote:
On 28 September 2017 at 11:39, Gunnar Morling
> 2017-09-28 11:28 GMT+02:00 Vlad Mihalcea <mihalcea.vlad(a)gmail.com>:
>> It's because not all database support ARRAY or JSON.
>> We've been discussing this on the mailing list (around one year ago)
>> remember we concluded that we can only add these types to ORM core
>> if the vast majority of the Hibernate-supported database offer JSON or
> I see. A separate project/repo under the Hibernate umbrella could be an
> alternative, too ("Hibernate Extras" or so). I.e. some middle ground
> between part of ORM proper and fully being 3rd party.
I'd (eventually) aim to include it in the hibernate-orm repository,
but as a separate jar?
So people can take it or ignore it depending on their needs, yet we
can all help making sure it keeps working for future releases.
I would not incorporate it into the hibernate-core artifact so that we
can exclude it from inclusion in e.g. WildFly until we feel it's ready
No rush though, I guess it would be easier to wait for some 6.0 branch
to be stable.
> Also, even if we add support for them, it's improbable that we are going
>> backport it to 5.1, 5.0, 4.3, 4.2 and 4.1. So, since my blog readers
>> requested me to provide these types via Maven Central, I decided to
>> them in a new library.
>> If more and more databases add support for JSON, we could add support
>> it in 6.0.
>> For ARRAY, I doubt that more DBs will support it if they haven't done it
>> by now.
>> On Thu, Sep 28, 2017 at 9:47 AM, Gunnar Morling <gunnar(a)hibernate.org>
>>> Hey Vlad,
>>> I recently learned about your "Hibernate Types" project .
>>> see support for JSON, arrays, etc!
>>> Out of curiosity, though, why did you decide to make it a separate
>>> instead of adding these very useful types to Hibernate itself? Seems
>>> be easier for people to us them that way.
>>> hibernate-dev mailing list
> hibernate-dev mailing list
hibernate-dev mailing list