+1
But I'd really like to see - for example - Oracle providing free to
use (and hosted) RDBMS instance, 10gen a MongoDB instance, etc.. so
they can update it as they see fit and deal with the maintenance
aspects of it (and licencing + execution costs).
Ideally if someone - like Andrew in this case - would be willing to be
notified from continuous integration failures and make sure someone
will help, then I think it would be more effective to keep the code in
Hibernate.
On 3 May 2013 10:29, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
But we can definitely have a wiki page or even better a table in the
documentation for third party dialects and where they are hosted.
That' cheap for us and keep the ecosystem thriving.
Emmanuel
On Fri 2013-05-03 17:17, Strong Liu wrote:
> I think the main reason is the lack of dev resource, if someone is willing to promise
that long time contribution / maintains, I'm fine with that, or it will just become
some dead code that we don't have knowledge nor time to maintains.
>
> On May 3, 2013, at 4:47 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> > Why not? Especially as Hana looks extremely interesting.
> >
> > I recall some discussion about having the database vendors maintain them, but to
go that route we could at least document how it works and make sure it's easy enough
for end users.
> >
> > I think I'd prefer to see if database vendors are willing to donate hosting
of a public instance of their db for test purposes.
> > On 3 May 2013 04:02, "Strong Liu" <stliu(a)hibernate.org> wrote:
> > IIRC there was an agreement that we'd not accept new dialect anymore
> >
> > On May 2, 2013, at 3:41 AM, Andrew Clemons <andrew.clemons(a)gmail.com>
wrote:
> >
> > > I'd like to follow up on the discussion started here[1]. I was asked
to
> > > port an existing application to Hana, so my first task was to write a
> > > hibernate dialect for it. I've completed this and so far it is working
> > > nicely in the integration tests for the application. My app is still
> > > using Hibernate 3.3, so that was my starting point, but with a few small
> > > changes it also compiles against the current git master. Is there still
> > > interest in such a dialect? Should I open a jira ticket and submit a
> > > pull request?
> > >
> > > Thanks,
> > > Andrew
> > >
> > > [1]
https://community.jboss.org/wiki/DoHibernatePlanToSupportSAPHANADatabase
> > >
> > > _______________________________________________
> > > hibernate-dev mailing list
> > > hibernate-dev(a)lists.jboss.org
> > >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> > -------------------------
> > Best Regards,
> >
> > Strong Liu <stliu at hibernate.org>
> >
http://about.me/stliu/bio
> >
> >
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> -------------------------
> Best Regards,
>
> Strong Liu <stliu at hibernate.org>
>
http://about.me/stliu/bio
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev