Hmm, so you are thinking about an extra module which contains ALL the DB
Let's say I'm an Oracle user and I want some specific stuff but I don't
want to have neither the PgObject nor the Jackson dependency.
What should I do in this case?
Can't we have optional modules which are pluggable to the hibernate-core?
If some DB specific module is on the classpath, use them.
On Sat, Jul 1, 2017 at 8:05 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
On 1 July 2017 at 18:00, Vlad Mihalcea
> For Ipv4 Type, we need a dependency for PgObject.
> For JSON, we need the Jackson dependency, and I would not add those to
> That's why I'm thinking of an extra module.
Since each of these two have different dependencies, wouldn't it be
better to have two extra modules?
> On Sat, Jul 1, 2017 at 7:48 PM, Arnold Gálovics <
>> Hi Vlad,
>> "any other features that cannot be added into the hibernate-core
>> are DB-specific."
>> Aren't Dialects in Hibernate DB specific? Why is there a reason not to
>> support some DB specific feature in Hibernate core?
>> Isn't it possible to have DB specific Hibernate modules? For example
>> hibernate-core contains the core of Hibernate (as the name suggests) but
>> everything else DB specific is in a specific module, Dialects, custom
>> types, etc.
>> If you could clarify this for me, that would be great as I don't know
>> historic reasons. :-)
>> Thank you guys!
>> On Sat, Jul 1, 2017 at 6:31 PM, Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
>>> Someone asked me if I can supply the JSON Type as a separate module so
>>> it can be grabbed from Maven Central:
>>> I wonder if we should supply a hibernate-extras where we include
>>> non-standard features:
>>> - JSON Types
>>> - ARRAY types
>>> - Ipv4 Types
>>> or any other features that cannot be added into the hibernate-core
>>> they are DB-specific.
>>> Let me know what you think.
>>> hibernate-dev mailing list
> hibernate-dev mailing list