[fluent-nhib] Re: not found attribute on ManyToOnePart

2009-01-29 Thread James Gregory
Just FYI, this has been implemented now. On Wed, Dec 17, 2008 at 8:54 PM, Marco wrote: > > I'm currently setting the 'not-found' attribute by using the > SetAtttribute method, but a fluent implementation would be nice! > > .SetAttribute("not-found", "ignore"); > > Thanks > Marco > > > --~--~---

[fluent-nhib] Re: Reveal for double, int, ...

2009-01-29 Thread James Gregory
Just committed a fix for this, let me know if you have any more problems. On Wed, Jan 28, 2009 at 11:40 PM, Jan Van Ryswyck wrote: > > Wow, you're fast. Happy bug hunting and keep up the good work. :-) > > > On 29 jan, 00:37, James Gregory wrote: > > Very interesting. That's a bug. Added to the

[fluent-nhib] Re: Need some explanations about LazyLoad method

2009-01-29 Thread James Gregory
Luis: I've just committed a change that'll affect this. I've added LazyLoad to subclass, and I've updated everything to use a Not property instead of explicit NotXXX methods; that way we won't forget about doing a Not something in the future. So it's now: LazyLoad() and Not.LazyLoad(), these are av

[fluent-nhib] Re: Urgence:How to map this situation?

2009-01-29 Thread James Gregory
Well, the Where statement is now mapped. If ObjType is in your class (and you are using the default column name) you can do this: HasMany(x => x.Comments) .Where(x => x.ObjType == "Product"); If it isn't in your object, or it is but the name differs from the database column, then you should do

[fluent-nhib] Re: Help with PagedList : List with Fluent NHibernate

2009-01-29 Thread James Gregory
Well, for starters you don't want your list to be in the same namespace otherwise the automapper will just assume it's an entity that needs mapping. As for your mapping, you really don't want many PagedList, you want many T, with a custom collection of PagedList. We don't have explicit support for

[fluent-nhib] Re: Help with PagedList : List with Fluent NHibernate

2009-01-29 Thread Brian
I just did an update and tried again with no luck. Same error. I still have the PagedList : List in a namespace that I am not mapping using Fluent. Unfortunately, I still get the same error regarding ContainsGenericParameters Any other suggestions?? Thanks so much, Brian On Jan 29, 11:59 am,

[fluent-nhib] Re: Help with PagedList : List with Fluent NHibernate

2009-01-29 Thread James Gregory
When was the last time you did an update? I fixed a bug a couple of days ago todo with that exception. On Thu, Jan 29, 2009 at 5:36 PM, Brian wrote: > > No. I took it out because I didn't want Fluent to look at it. Does > it need to be? I have tried both ways and have gotten different > error

[fluent-nhib] Re: Help with PagedList : List with Fluent NHibernate

2009-01-29 Thread Brian
No. I took it out because I didn't want Fluent to look at it. Does it need to be? I have tried both ways and have gotten different errors. If it is IN the namespace, I get: "Late bound operations cannot be performed on types or methods for which ContainsGenericParameters is true." In the Inv

[fluent-nhib] Re: Traversing a Description Class

2009-01-29 Thread timeisfire8
James Thanks for the rapid response and apologies for the delay but I have been quite unwell for a couple of days. I had seen your blog post on cleaning up the SubClass syntax but either I am missing something (very probable) or it does not solve my problem. The examples in your post all seem to

[fluent-nhib] Re: Wrong class exception with discriminator sub class

2009-01-29 Thread James Gregory
Firstly, I can tell by your code that you're on an older version of Fluent NHibernate - I'd advise updating as the join stuff has changed. You should read this for the join syntax changes: Fluent NHibernate SubClass syntax changes

[fluent-nhib] Wrong class exception with discriminator sub class

2009-01-29 Thread chris
Hi all, I have the following scenario that I'm struggling to map out in fluent. Can anyone advise? Tables: === TypeA TypeB User Relationships: === User table has a "type" discriminator column and a "typeID" so when the type column is A the typeID will point to the TypeA subtable. W