Interesting. How are you dealing with the problem that old class maps won't compile (because, for example, you renamed a property)?
On Sat, Jul 18, 2009 at 10:46 PM, Nercury <[email protected]> wrote: > > My bad, AutoMapping can do that. Sorry for my stupidity. > > On 18 Lie, 01:54, Nercury <[email protected]> wrote: > > I am currently implementing[1] a way to "fluently" generate > > upgrade scripts and I need to store both old and current > > ClassMap<T> mappings. To differentiate between them, > > I am thinking about some kind of [Obsolete()] attribute, > > so that PersistenceModel would not pick up old types. > > > > Is there easy way to inject some kind of filter or maybe > > more obvious way to do it? > > > > [1] Implementation right now is in the flux, but if it is successfull > > i am going to release it as FluentNUpgrade project. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
