Hey Vlad, our approach had been to accept new Dialects only if:
1. Someone or some entity is willing to develop it
2. Someone or some entity is willing to maintain it *long term*
3. The community demands it (either through the ML, JIRA votes, noise
on the forums or externally, etc.)
Too often, Dialects are created and abandoned. Even worse, a Dialect in
ORM is used as an advertisement of sorts for the DB vendor.
If they want to create the Dialect, fantastic. But unless #2 and #3 are
true, we typically ask that they release the Dialect on their own,
outside of the core ORM project.
So, the next step would be to create a JIRA, gauge the community need,
and start a discussion with Altibase to find out if this is a long term
commitment for them...
On 04/14/2016 04:00 AM, Vlad Mihalcea wrote:
We have another Dialect coming as a pull request:
In my opinion, we should integrate new Dialects and just document which
ones are maintained by us, and which ones are under development by other
For the Altibase database, the Dialect was sent by an Altibase employee, so
it is their interest to maintain it as well.
hibernate-dev mailing list