here are some related topics:
http://lists.jboss.org/pipermail/hibernate-dev/2010-April/005094.html
http://lists.jboss.org/pipermail/hibernate-dev/2010-April/005101.html
http://lists.jboss.org/pipermail/hibernate-dev/2010-April/005102.html
http://lists.jboss.org/pipermail/hibernate-dev/2008-September/003323.html
we (hibernate team) would suggest DB vendors maintain the hibernate dialect themselves,
like delivery the dialect class within jdbc driver.
there are some reasons that we recommended this way:
1. resources, we have limited developer resources and testing environment resource, for
example, i don't think we have qa resources to maintain a CURBID instance for
testing/CI.
2. since Dialect is the main contract between hibernate and DB, so, if DB has any new
release, it can update the dialect as well, and no need to wait for hibernate release.
meanwhile, we would like to help db vendors to set up a hibernate ci environment to make
sure the dialect/hibernate works well on the DB.
and thanks for working on this dialect :D
-----------
Strong Liu <stliu(a)hibernate.org>
http://hibernate.org
http://github.com/stliu
On Jul 14, 2011, at 3:12 PM, 에센 사그노브 wrote:
Hi,
I am the CUBRID open source RDBMS Project Manager. Our parent company NHN has extensively
been using Hibernate in its services together with CUBRID Database Server.
Here I would like to attach the CUBRIDDialect.java class file which supports CUBRID
version 8.3.0 and higher (8.3.0, 8.3.1, and current stable 8.4.0) that we want to submit
to Hibernate project.
If I should create an issue in JIRA, please let me know which project is the most
appropriate.
Regards,
Esen Sagynov.
CUBRID Project Manager.
http://www.cubrid.org
http://twitter.com/cubrid
http://facebook.com/cubrid
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev