I can't swear on it, but id did look like the code would do something sensible with e.g. "String(2)". You can try to create a minimal test case using XML mapping to verify, or you can try hacking FluentNH to make it propagate the length - shouldn't be too difficult.
/Oskar 2012/12/5 Svend Tofte <[email protected]>: > > > On Wednesday, December 5, 2012 10:46:24 PM UTC+1, Svend Tofte wrote: >> >> >> On Wednesday, December 5, 2012 7:36:37 PM UTC+1, Oskar Berggren wrote: >>> >>> What is the XML that FluentNH generates for TypeFactory.GetStringType(2)? >>> >>> /Oskar >>> >> >> So seems like the length parameter is not propagated down to the actual >> mapping. FluentNH or NH maybe think its not needed? Inspecting the type >> returned from TypeFactory, it looks correct, Length = 2, and all that. >> > > Just tried overriding the filter type definition using > FluentConfiguration.ExposeConfiguration, which exposes the > NH.Cfg.Configuration instance, and setting it once more (to > TypeFactory.GetStringType(2)), but that has no effect as well. > > -Svend > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/nhusers/-/DrkbGTij6hUJ. > > 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. -- 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.
