The suggestion and discussion happened here: http://ode.markmail.org/message/agdihktklaerqes6?q=change+roadmap As Rafal stated, the benefit would be that easier migration for Hibernate User from native Hibernate to JPA Hibernate, also we can finally drop the dao-hibernate module.
I wouldn't think two schemas would be exactly same, but most of the schemas would be same. The other thought for this vote would be trying to know that how many users are really using the OpenJPA, I don't think maintaining two DAO implementation (As they are also some difference between JPA-OpenJPA and JPA-Hibernate database schema) is a very good choice for one project. Regards Jeff On Thu, Jun 17, 2010 at 6:32 AM, Guillaume Nodet <[email protected]> wrote: > Which suggestion ? I haven't seen much discussion. It sounds like a > major incompatible change for OpenJPA users. What's the benefit ? > Can the two schema be exactly the same or not ? > > On Wed, Jun 16, 2010 at 17:07, Jeff Yu <[email protected]> wrote: > > Hi team, > > > > This is a follow-up vote for the Rafal's suggestion, which is to try to > make > > JPA implementation's table schema is as same as possible with the > > dao-hibernate module db schema. > > This means it would cause users who use OpenJPA will have the db schema > > changes dramatically from the 1.3.5 release, in the other hand, the > > Hibernate users might just need > > to do some small schema update when switching it from native Hibernate to > > the JPA Hibernate implementation. > > > > So I think we need an vote here. > > > > Personally, I'd like to have one static schema, given a lot of users > choose > > hibernate, here is my +1. > > > > Regards > > Jeff > > > > -- > > Cheers, > > Jeff Yu > > > > ---------------- > > blog: http://jeff.familyyu.net > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Jeff Yu ---------------- blog: http://jeff.familyyu.net
