Ah ok, thanks! I was unsure if it was related to the automapping issue discussed on this list.
Right now the only way I can get passed it, removing the AddTypeConvention from the Conventions constructor, and add my own in my own code. /Asger On 12 Feb., 23:55, James Gregory <[email protected]> wrote: > I believe somebody else raised this earlier, it's on my list of things to > review as soon as I get the chance. > Just FYI both your messages were in the message queue, so I removed your > original one. > > On Thu, Feb 12, 2009 at 8:39 PM, blindwillie <[email protected]> wrote: > > > Hi > > > I may have been double posting, but I could not find my first mail on > > the list to submit additional information. I apologize if it's just me > > being too impatient. > > > Well... My former post was about mapping nullable enums, but I now > > find, that this applies to all enums that maps to an int column in the > > DB. > > > I use the mapping: Map(x => x.EnumType).CustomTypeIs(typeof(int)) > > > It has worked before, but I have now updated to trunk, and now I get > > an NHibernate exception when i get the entity, that says "Cannot parse > > 2 as EnumType". > > > Any one knows why? > > > Sincerely, Asger > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
