I was working on a bit of a refactor to how the whole PartPosition thing was working after I discovered the issue with Version/Discriminator appearing in the wrong order depending on when they were added to a class map. I've incorporated the test you created on the patch into my working refactor (and it's passing :) ). I'll try and push my changes up here soon for you two.
On Fri, Apr 10, 2009 at 2:32 PM, Lothan <[email protected]> wrote: > > Much, much better. Thank you. > > -------------------------------------------------- > From: "Jon Kruger" <[email protected]> > Sent: Thursday, April 09, 2009 12:30 PM > To: "Fluent NHibernate" <[email protected]> > Subject: [fluent-nhib] Re: Ordering of columns when generating schema for > an > auto-mapped table > > > > > Here's the issue and the patch: > > http://code.google.com/p/fluent-nhibernate/issues/detail?id=183 > > > > On Apr 9, 11:25 am, Jon Kruger <[email protected]> wrote: > >> I found the problem and fixed it... I'm creating an issue and > >> submitting a patch, but I'm getting server errors right now. I'll try > >> again after lunch. > >> > >> On Apr 9, 10:31 am, Jon Kruger <[email protected]> wrote: > >> > >> > I'm using auto-mapping and I'm also using ISessionSource.BuildSchema() > >> > to create my database tables for me. I have audit fields in all my > >> > tables (e.g. CreatedBy, CreatedDate, etc.), and I want these to be the > >> > last columns in every table (currently they're sprinkled all over the > >> > place in the table). Is there a way I can specify an order for the > >> > columns? > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
