I believe this is the scenario that maggie has that wasn't fixed with 444.
I'll be able to check into it later today :)
Just as a general note Maggie, the fix in 444 was for writing out properties
in the order they were added to a class mapper. It's possible that this
isn't what's wrong, but it's that the fields are being added by the
automapper in an order not consistent with your declaration order.

On Sat, Apr 18, 2009 at 3:45 AM, Paul Batum <paul.ba...@gmail.com> wrote:

>
> Is this somehow different to the problem that you've been discussing
> in the other thread, that was supposed to be fixed in revision 444?
>
> On Fri, Apr 17, 2009 at 2:39 AM, MaggiePlusPlus
> <maggielongsh...@gmail.com> wrote:
> >
> >
> > Here is the code I am using to create my database and to export the
> > xml mapping files:
> >
> >  return Fluently.Configure()
> >                    .Database(JetDriverConfiguration.Standard
> >                                  .ConnectionString(c => c
> >                                                             .DatabaseFile
> > (FileName)
> >                                                             .Provider
> > ("Microsoft.ACE.OLEDB.12.0")
> >                                                             .Username
> > ("")
> >                                                             .Password
> > ("")))
> >                    .Mappings(m =>
> >                              m.AutoMappings.Add(
> >
> >
> AutoPersistenceModel.MapEntitiesFromAssemblyOf<IPCApplication.Entities.Model.Pipe>
> > ()
> >                                      .Where(type =>
> > type.Namespace.EndsWith("Model")))
> >                                  .ExportTo(@"ExportAutoMaps"));
> >
> > one sample input/output is:
> >
> >    public class InspectionPlan
> >    {
> >        public virtual int Id { get; private set; }
> >
> >        public virtual string PipelineName { get; set; }
> >        public virtual string PipeName { get; set; }
> >        public virtual string CreationDate { get; set; }
> >
> >    }
> > <?xml version="1.0" encoding="utf-8"?>
> > <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2"
> > assembly="IPCApplication.Entities, Version=1.0.0.0, Culture=neutral,
> > PublicKeyToken=null" namespace="IPCApplication.Entities.Model">
> >  <class name="InspectionPlan" table="`InspectionPlan`"
> > xmlns="urn:nhibernate-mapping-2.2">
> >    <id name="Id" type="Int32" column="Id">
> >      <generator class="identity" />
> >    </id>
> >    <property name="PipeName" type="String">
> >      <column name="PipeName" />
> >    </property>
> >    <property name="CreationDate" type="String">
> >      <column name="CreationDate" />
> >    </property>
> >    <property name="PipelineName" type="String">
> >      <column name="PipelineName" />
> >    </property>
> >  </class>
> > </hibernate-mapping>
> >
> > All is working except that the columns are not kept in order. What do
> > I need to do to retain the input order?
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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 from this group, send email to 
fluent-nhibernate+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to