1.) Id.GeneratedBy.Foreign(“Account”) should really be more like Id.GeneratedBy.Foreign(x=>x.Account). But yes, please raise an issue with it so we can keep it on the radar :)2.) I'd definitely say you could create an issue that combines the need for Readonly and autonumber attributes on references. For now, just keep using a SetAttribute to get by. 3.) Enum handling, map it to a custom type of int for the time being. There's a downside to this though, which is that it flags the object as dirty the instant it's pulled back from the database, due to the type conversion that gets performed to turn the int into an enum. This issue should already be logged<http://code.google.com/p/fluent-nhibernate/issues/detail?id=168> if you wanted to star it and get updates when it's resolved. I believe there's even a patch there for you if you didn't want to use the int trick. 4.) Just raise the issue on google code, and ask for a type change in your issue and one of us (project members) will come by and change the type to something that makes a bit more sense. If you want, you can prefix your issue subject with the type it should be (Feature Request: , Bug: , Etc:)
On Sat, Apr 25, 2009 at 5:03 AM, Rob <[email protected]> wrote: > > I've just switched from *.hbm.xml mapping to NHF regular mapping (not > automapping). > I have still few difficulties with the full migration. Possibly this > is due to the fact that I'm using legacy database with complex schema. > Most common thing is that UseCompositeId.WithKeyProperty doesn't > support custom types. In my case I need to use TrimmedString user type > because my database is padding string values with spaces. > Fortunately I see that issue 199 is created and assigned so I hope > that soon this will be solved. > Next thing is following: > Id.GeneratedBy.Foreign(“Account”) > I think that it should be rather > Id.GeneratedBy.Foreign<Account> > but there is no such possibility. Should I raise an issue on this? > Next things > - ReadOnly attribute is not available for References; > - Autonamber is not available for References; I think also that it > should be renamed to Insertable rather because current name is > misleading; also Updatable would be very useful instead of > SetAttribute. > > Then I have some doubts about enum handling. For example I'm using > System.DayOfWeek type mapped into integer column. In hbm.xml file I've > set type="System.DayOfWeek". In NHF I've set CustomTypeIs<DayOfWeek> > but I see that generated hbm.xml file contains GenericEnumMapper. Is > this correct? > > Finally I don't know how to raise an issue into code.google.com > correctly. When I want to do this the only kind of issue is "Defect". > As you see my list of complains does not contain bugs in NHF, these > are enhancements rather. Similar things are with patches - I've > provided a patch 147 to handle my database in NHF but this is also > classified as "Defect" which is also not correct. > Is there a possibility to raise an issue using more precise > classification? On nhjira.koah.net I can raise an issue as a patch, > bug, new feature or improvement. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
