[fluent-nhib] Integrating with Rhino.Commons

Hey all, After messing around with it for a bit I finally got FNH and Rhino.Commons to play nice. Check this out, if interested ( http://robkitson.net/archive/2009/02/02/using-fluentnhibernate-and-rhino-commons.aspx ). -rk --~--~-~--~~~---~--~~ You received this m

[fluent-nhib] Re: First attempt at parent/child not working

you forgot the "cascade" for the collection (HasMany) On Tue, Feb 3, 2009 at 3:56 AM, Lars wrote: > > I'm very new to NHibernate and Fluent. I've done OK with mapping a > single object, but my first object containing a collection is not > working. It seems that my mapping is not saving the coll

[fluent-nhib] Re: Fluent configuration API

How dare you turn my entire NHibernate SessionFactory creation into a singlea private static readonly field in my manager class! As always great work James, FNH never ceases to amaze me at how fast it's been progressing. I'm pretty sure I did catch a bug with this change, I have my connection st

[fluent-nhib] Re: Update FNH from NH 2.0.0.4 to 2.0.1.4

This is good news no more having to play assembly version mambo. On Feb 2, 8:16 pm, James Gregory wrote: > I've upgraded FNH to run on 2.0.1GA of NHibernate, and Build 1.0.0.Alpha 696 > of NHibernate.Linq. > > On Mon, Feb 2, 2009 at 2:01 PM, James Gregory wrote: > > > Yep, sounds like a plan. >

[fluent-nhib] First attempt at parent/child not working

I'm very new to NHibernate and Fluent. I've done OK with mapping a single object, but my first object containing a collection is not working. It seems that my mapping is not saving the collection. The parent table is ZipcodeSet and the child collection is ZipcodeSetDetail. Can anyone see what I h

[fluent-nhib] Re: Update FNH from NH 2.0.0.4 to 2.0.1.4

I've upgraded FNH to run on 2.0.1GA of NHibernate, and Build 1.0.0.Alpha 696 of NHibernate.Linq. On Mon, Feb 2, 2009 at 2:01 PM, James Gregory wrote: > Yep, sounds like a plan. > > > On Mon, Feb 2, 2009 at 1:37 PM, Troy Goode wrote: > >> >> Oh, and I did eventually get it to work by recompiling

[fluent-nhib] Heads up - breaking database config change

Guys, Just a heads up, I've made some changes to the database configuration API. Reason being that it wasn't entirely gelling with the Fluent.Configure API, and there had been some suggestions for improvements tha

[fluent-nhib] Fluent configuration API

Guys, Yesterday I committed a reasonably large commit that added a new API to FNH, it's purpose is to tie together our existing APIs in such a manner to make it extremely easy to configure an entire application with FNH. This blog post outlines the main usage scenarios: Fluent NHibernate: Configur

[fluent-nhib] Re: ManyToManyAutoMapper - Possible Bug

I've added some tests and made the code use less reflection. On Tue, Feb 3, 2009 at 1:03 AM, James Gregory wrote: > I've added it to my todo list, but it's up for grabs if anyone wants to > tackle it before I do. > > > On Mon, Feb 2, 2009 at 2:02 PM, James Gregory wrote: > >> Indeed we don't, it

[fluent-nhib] Re: Troubleshooting AutoPersistenceModel problems

I could provide a sample if you want to see it - but if CompileMappings puts them all somewhere where WriteMappingsTo can actually write them out pre-configure, I should be good to go. On Feb 1, 4:53 pm, Andrew Stewart wrote: > Hi > > I understood what you meant, but I couldnt get it to fall ove

[fluent-nhib] Re: ManyToManyAutoMapper - Possible Bug

I've added it to my todo list, but it's up for grabs if anyone wants to tackle it before I do. On Mon, Feb 2, 2009 at 2:02 PM, James Gregory wrote: > Indeed we don't, it concerns me greatly. I should've wrote a test with this > fix really, but I was more concerned with just getting it out. > Idea

[fluent-nhib] Re: ManyToManyAutoMapper - Possible Bug

Indeed we don't, it concerns me greatly. I should've wrote a test with this fix really, but I was more concerned with just getting it out. Ideally I'd like to get the automapper to not have to rely on reflection at all (possibly some kind of interface might help), but at the very least we need to m

[fluent-nhib] Re: Update FNH from NH 2.0.0.4 to 2.0.1.4

Yep, sounds like a plan. On Mon, Feb 2, 2009 at 1:37 PM, Troy Goode wrote: > > Oh, and I did eventually get it to work by recompiling FNH - but since > 2.0.1 is the currently advertised release of NH, I think it would be a > good idea to update FNH as well. > > On Feb 2, 8:30 am, Troy Goode wro

[fluent-nhib] Re: Update FNH from NH 2.0.0.4 to 2.0.1.4

Oh, and I did eventually get it to work by recompiling FNH - but since 2.0.1 is the currently advertised release of NH, I think it would be a good idea to update FNH as well. On Feb 2, 8:30 am, Troy Goode wrote: > Any plans to update Fluent to use the 2.0.1 GA release of NHibernate? > I've been

[fluent-nhib] Re: ManyToManyAutoMapper - Possible Bug

Hmm, so I am guessing we have no unit tests for that code? With all that reflection, it seems pretty fragile. On Mon, Feb 2, 2009 at 6:58 AM, James Gregory wrote: > Ok, I've committed a fix for this. Let me know if anything else crops up. > > On Sun, Feb 1, 2009 at 7:52 PM, James Gregory wrote: >

[fluent-nhib] Update FNH from NH 2.0.0.4 to 2.0.1.4

Any plans to update Fluent to use the 2.0.1 GA release of NHibernate? I've been trying to get Fluent working with the recent NHibernate.Linq alpha (http://groups.google.com/group/nhusers/browse_thread/thread/ b7a3f537f4cbf46d) and have had some difficulties. NHibernate.Linq is built off of 2.0.1.4

[fluent-nhib] Re: Change to HasMany

Ok, it's in for HasManyToMany too. On Mon, Feb 2, 2009 at 12:41 PM, James Gregory wrote: > Guys, > I just committed a nice little API change you should be aware of > (r261 > ). > > The type for HasMany can now be inferred in most c

[fluent-nhib] Change to HasMany

Guys, I just committed a nice little API change you should be aware of (r261 ). The type for HasMany can now be inferred in most cases. HasMany(x => x.Users) can now be: HasMany(x => x.Users) As long as the property type derives