In terms of actually getting it included? Well just passing the testsuite is of course a first step.
Beyond that though I am a little leery of adding new dialects "just because someone contributed (dumped) it". The reasoning is quite simple. We have quite a bit of this type of "integration code" in Hibernate already that goes unmaintained for long spurts of time. And truth be told a lot of it deals with DB2 variants and WebSphere which of course makes me a little even more leery here. So for this aspect we would need you (or someone) to take ownership of this code. If you agree to that we can discuss those particulars off list. Also realize that the contributions *must* be LGPL. We have had issues with that previously with regards to IBM employees and IBM's legal teams from LGPL FUD. To that end, y'all must sign a contributor agreement accepting the terms of LGPL and agreeing to your contributions being made publicly available under its terms. Also, how many Hibernate users are actually using solidDB? On 04/16/2010 10:48 AM, Niall DOWNEY wrote: > Hi Chris, > thanks for the info. Is it just a case of checking out the latest Test > Suite code from CVS and running what are probably JUnit tests ?. Is there > anything else we need to do or be aware of ?. > > Regards, > > Niall > > IBM Ireland Information Services Limited registered in Ireland with number > 97537. Registered office: Oldbrook House, 24-32 Pembroke Road, > Ballsbridge, Dublin 4 > > > > Chris Bredesen > <cbrede...@redhat > .com> To > Sent by: hibernate-dev@lists.jboss.org > hibernate-dev-bou cc > n...@lists.jboss. > org Subject > Re: [hibernate-dev] solidDB > Hibernate dialect ? > 16/04/2010 16:25 > > > > > > > > > > On 04/15/2010 07:39 AM, Niall DOWNEY wrote: >> Hi All, >> I work for IBM and we are investigating adding our solidDB dialect to the >> existing set in Hibernate. Can someone tell me how we go about this and > who >> should we talk to ?. >> >> Apologies if this is off-topic but it was suggested in the "Hibernate >> Users" forum that I try posting here. > > I'd start by filing a JIRA against Hibernate Core: > > http://opensource.atlassian.com/projects/hibernate/ > > Attach your Dialect to the issue. Run the test suite against your > dialect and learn what works and what doesn't. The best thing we can do > for users of a Dialect is set expectations about known issues. > > Hope this helps, > > Chris (who has little/no say in what gets included, just trying to help) > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- st...@hibernate.org http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
