Thanks for the hint. I will test it with version 2.1 This is a major issue for us, because we are on 2.0 now and I have a user type just to make sure that the precision is on 36,18. If I need to declare the precision when ever I map a decimal, I have a lot of work and a maintenance problem too.
I actually hope to upgrade to 2.1 soon, but for the moment I have to make things work quickly ... I actually don't know what I should do now. I fear that the only option is to go through all the mapping files and define the precision ... :-( On 1 Jul., 15:23, Roger Kratz <[email protected]> wrote: > There were some issues with decimal db > typehttp://nhjira.koah.net/browse/NH-1594 > > Are you using latest nh bits? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Stefan Steinegger > Sent: den 1 juli 2009 13:54 > To: nhusers > Subject: [nhusers] Defining a user type for decimal with precision > > I have a user type which specifies a decimal with precision and scale > like this: > > public IType[] PropertyTypes > { > get > { > return new [] > { > TypeFactory.GetDecimalType(36, 18), > TypeFactory.GetStringType(100) > } > } > } > > The problem is, when generating the schema, the string is fine, > defined with a length of 100 (default is 255), but the decimal is > still define as decimal(19,5). > > Is this a bug, or am I doing something wrong? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
