+1 on the concept and knowing how it goes
On Jul 19, 2:37 am, Paul Batum <[email protected]> wrote:
> Heh. I gave up on this idea a while ago because I just couldn't stand having
> old versions like that. Let me know how it goes :)
>
> On Sat, Jul 18, 2009 at 11:34 PM, Nercury <[email protected]> wrote:
>
> > Basically, for now, idea is to have both class versions in assembly.
> > For example, if
> > for class "Person", i would also have old versions as "Person_0",
> > "Person_1", etc., plus
> > any changes registered between them. When I decide to rename some
> > field in Person, I
> > would need to:
> > - Copy Person class to Person_2
> > - Make changes to Person
> > - Map changes I made (example here in "InitUpgradeMap" method:
>
> >http://github.com/Nercury/fluent-nupgrade/blob/07bdd91750cccc125a8839...
> > )
> > - Up the database version and register this change (possibly, with
> > changes to other entities)
>
> > As I said, interface is highly in flux, it may be automatic later but
> > even manual way to register
> > changes would be awesome for now. I have some trouble understanding
> > whole picture of NHibernate
> > and FluentNHibernate, so if anyone want to help to push project
> > forward, please don't hestitate :)
>
> > On 18 Lie, 16:12, Paul Batum <[email protected]> wrote:
> > > 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
-~----------~----~----~----~------~----~------~--~---
