[fluent-nhib] Re: Constraints not making it to the database schema

2009-03-11 Thread James Gregory
Sorry guys, this one slipped under the radar. I'm swamped currently, but I should be doing a comb through of patches in the next few days. Filip: Hopefully you should be able to apply Steven's patch directly to your code for the time being. 2009/3/11 Filip Kinsky > > Is this applied to the trunk

[fluent-nhib] Re: Constraints not making it to the database schema

2009-03-11 Thread Filip Kinsky
Is this applied to the trunk? I'm just facing simmilar problems (on Oracle) - fields don't get length specified and FK names are generated randomly even though I specify both in my conventions... On 20 Ún, 01:47, Steven Lyons wrote: > Take II: This patch passes the tests. > > Index: src/FluentNH

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread Steven Lyons
Take II: This patch passes the tests. Index: src/FluentNHibernate.Testing/DomainModel/Mapping/ ClassMapXmlCreationTester.cs === --- src/FluentNHibernate.Testing/DomainModel/Mapping/ ClassMapXmlCreationTester.cs(revision 330) +++

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread Steven Lyons
James, Attached is a patch that gets most of the way there, I think. I added a test for the unique attribute and made changes similar to what you did for the previous fix. There is one test that isn't passing. The hbm is getting two lengths for strings now - the correct one on the column (length

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread James Gregory
Thanks for the heads up, I'll fix this asap. On Thu, Feb 19, 2009 at 10:27 PM, Steven Lyons wrote: > > It looks like same problem occurs with the length attribute. As with > the previous fix, when the column element is present in a property, as > it is the FNH hbm exports, the length should be on

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread Steven Lyons
It looks like same problem occurs with the length attribute. As with the previous fix, when the column element is present in a property, as it is the FNH hbm exports, the length should be on the column instead of the property. On Feb 19, 11:23 am, Steven Lyons wrote: > Hi James, > > The new fix

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread Steven Lyons
Hi James, The new fix has partly resolved the issue. The "not null" is now making it through to the schema but the unique constraint is still being dropped. s. On Feb 19, 9:35 am, James Gregory wrote: > There was a bug in the Not.Nullable code that I've just fixed, could you > confirm (or de

[fluent-nhib] Re: Constraints not making it to the database schema

2009-02-19 Thread James Gregory
There was a bug in the Not.Nullable code that I've just fixed, could you confirm (or deny) whether this has had any affect on your problem? On Thu, Feb 19, 2009 at 12:09 AM, Steven Lyons wrote: > > Hi All, > > I'm having a weird problem that hopefully someone might have some > thoughts about. > >