Try to explain because, even if there is no problem to make something public, to me your patch seems unneeded.
On Fri, Aug 13, 2010 at 1:32 PM, Patrick Earl <[email protected]> wrote: > We have been maintaining an internal patch to NHibernate for quite > some time, and I'd ultimately like to be able to run on an unpatched > version of NHibernate. The internal patch we use allows us to access > the mapping schema that NHibernate generates. This allows us to build > our own enhanced system for applying schema updates to the database. > I'd submit a patch, but I'm not really sure in which direction to go. > I'd love some feedback on how this might be done. > > Here's what our internal patch does to Configuration.cs: > > - private IMapping mapping; > + public IMapping mapping; > > - private ICollection<Table> TableMappings > + public ICollection<Table> TableMappings > > - private void SecondPassCompile() > + public void SecondPassCompile() > > Looking forward to hearing people's thoughts. > > Patrick Earl -- Fabio Maulo
