I'm not a committer, but I would be interested in helping out with the LINQ provider. The problem is that it's a bit too big a piece to just start working on, so is there someone heading up that work that I could talk to or is there any sort of design document out there?
I spent some time looking at what's already there for LINQ and the HQL engine to get an idea of how SqlStrings are generated in a similar engine, but it's clear there's still a lot of work to be done there. -Jon On Nov 24, 7:13 am, "Tuna Toksöz" <[EMAIL PROTECTED]> wrote: > I would like to _help_ anybody on Binder and will keep maintaining JIRA. I > have exams nowadays, so i don't write code much but i hope it will change > from next week for next 2 weeks. > > > > On Mon, Nov 24, 2008 at 1:11 PM, Fabio Maulo <[EMAIL PROTECTED]> wrote: > > - TransactionStrategy (TransactionFactoryFactory, > > TransactionContext, AdoNetContext....)So far talk about NH-Transaction and > > talk of Ado.NET transaction, is in practice, the same. > > We have a configurable transaction.factory_class but without alternatives. > > The target of this work is recreate the same infrastructure of involved > > classes H3.2.6 have and allow NH to create and work > > with ambient-transactions. > > > - EntityMode.Xml > > I had port some initial tests to support EntityMode.Xml. It is a very > > interesting feature that allow NH work with Xml as entities representation. > > Not fundamental for NH2.1 but would be useful to have it ASAP. > > > - Refactoring of Binders > > Old scheduled task. It is a refactoring of NHibernate.Cfg.XmlHbmBinding and > > related stuff. > > So far all binders are a mix between "Xml Parser" and the use of > > "Deserialize Hbm*" with some copy&paste. > > This work include: refactoring of XSD (to generate more reusable classes), > > refactoring of all binders to avoid XML parsing and use only deserialized > > classes, probably some little changes to NHibernate.Tool.HbmXsd. > > > - JIRA > > Obviously a good place to read about some pending work is the JIRA. There > > are a lot of "things" to do with various difficult levels. > > > NOTE: probably we must take a definitive decision about the pagination > > stuff of MsSQL2005 dialect. > > > To release NH2.1, IMO, we need at least the management > > of TransactionStrategy + some bug-fixing. > > > Personally I would like to begin a "new prj". The new prj is strictly > > related with NH-Core but I'll start it in another place (it is a really OLD > > story). > > The candidate code-name is : Rabbit's foot > > > -- > > Fabio Maulo > > -- > Tuna Toksözhttp://www.tunatoksoz.com > > Typos included to enhance the readers attention!
