Comments on: Migrating to Fluent NHibernate

By: Arnis L.

Arnis L. — Thu, 03 Dec 2009 07:57:50 +0000

@Jeffrey

Yeah, I’ve noticed that. And I’m glad i can learn so much from you guys.

Keep up the good work.

By: James Gregory

James Gregory — Wed, 02 Dec 2009 16:37:22 +0000

It’s always nice to hear success stories. I’m glad you guys had such a good experience.

By: Jeffrey Palermo

Jeffrey Palermo — Wed, 02 Dec 2009 15:50:10 +0000

@Arnis,
We at Headspring are early adopters, but we are very analytical about it. We have kept an eye on FNH, played with it a bit, but until we KNOW it is going to work the way we want it to in complex scenarios, we keep it out of client projects. Now that we know it will work for us, we are implementing quickly. Full conversions.

By: Kevin Dente

Kevin Dente — Wed, 02 Dec 2009 15:15:02 +0000

Are you guys looking at moving more toward automapping?

By: bogardj

bogardj — Wed, 02 Dec 2009 13:25:56 +0000

@Paul

We’re waiting on the nested composite elements, partly because we’re still not convinced it’s the right model in our situation anyway.

@Arnis

There was a lot of churn up until 1.0, so we were just biding our time

By: Gilligan

Gilligan — Wed, 02 Dec 2009 13:18:59 +0000

What is really interesting is to migrate from Castle.ActiveRecord mappings to Fluent NH and then still using ActiveRecord’s static functions for some classes.

By: Arnis L.

Arnis L. — Wed, 02 Dec 2009 08:37:51 +0000

I was wondering all the time, why no one from Headspring uses Fluent NHibernate? For me – it was like prerequisite to jump into NHibernate. Never actually liked xml.

By: Paul Batum

Paul Batum — Wed, 02 Dec 2009 06:55:51 +0000

I’m really glad to hear how painless your upgrade has been. Did you have to put off migrating some of your .hbms due to features we don’t support yet? I seem to recall something about nested composite elements?