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 stevenly...@gmail.com wrote:
Take II: This patch passes the tests.
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 stevenly...@gmail.comwrote:
Hi All,
I'm having a weird problem that hopefully someone might have some
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 stevenly...@gmail.com wrote:
Hi
Thanks for the heads up, I'll fix this asap.
On Thu, Feb 19, 2009 at 10:27 PM, Steven Lyons stevenly...@gmail.comwrote:
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
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
Take II: This patch passes the tests.
Index: src/FluentNHibernate.Testing/DomainModel/Mapping/
ClassMapXmlCreationTester.cs
===
--- src/FluentNHibernate.Testing/DomainModel/Mapping/
ClassMapXmlCreationTester.cs(revision 330)
+++
