[fluent-nhib] Re: Many-to-one and class attribute or References(...)

ROTECTED]> wrote: > >> Hi Pavel, >> >> I will be looking at and applying both your patches tomorrow. >> >> Many thanks, >> >> Paul Batum >> >> >> On Sun, Oct 19, 2008 at 7:18 PM, Pavel Samokha < >> [EMAIL PROTECTED]> wrote:

[fluent-nhib] Many-to-one and class attribute or References(...)

set it. -- Yours sincerely, Pavel Samokha --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe f

[fluent-nhib] Re: Identity type must be integral , but it can be nullable

nullable types for their primary > keys. > > Paul Batum > > On Tue, Oct 7, 2008 at 10:07 PM, Pavel Samokha <[EMAIL PROTECTED]>wrote: > >> >> Found another problem - Fluent NHibernate not supports nullable types >> as Id's (I prefer null instead of 0 f

[fluent-nhib] Identity type must be integral , but it can be nullable

Found another problem - Fluent NHibernate not supports nullable types as Id's (I prefer null instead of 0 for unsaved values) throws exception - Identity type must be integral (int, long, uint, ulong). So need to change IdentityGenerationStrategyBuilder.isIntegralType to add nullables (and I thi

[fluent-nhib] Re: "length" attribute and conventions

t be overridden by them. > > The behaviour you witnessed can indeed be confusing, we probably need to > spend some time looking at how conventions are applied. > > Paul Batum > > On Mon, Oct 6, 2008 at 12:07 AM, Pavel Samokha <[EMAIL PROTECTED]> wrote: > > > Ouh, I didn

[fluent-nhib] Re: "length" attribute and conventions

od? The SetAttribute method is really > only there for situations where we haven't implemented the feature yet and > its causing people problems. > > On Sun, Oct 5, 2008 at 10:52 PM, Pavel Samokha <[EMAIL PROTECTED]> wrote: > > > Playing today with Fluent NHibernate

[fluent-nhib] "length" attribute and conventions

Playing today with Fluent NHibernate (from trunk) while prototyping new project I found annoying thing - SchemaExport always produce me "nvarchar(100)" for strings - so i try to understand why. I used the following: Map(x => x.Name).SetAttribute("length","1000"); And found that "length" attribut