> > There would be no need for you do ANY manual
> > mapping with XML files!
>
> And that is good ?
It's "good" in the sense that you can quickly (in terms of development
time) persist certain commonly used object oriented structures,
without having to learn what is in effect a new language for mapping,
or worrying about exactly how your classes will map to tables in the
DB.
Within certain limitations, it "just works". In my case, at least,
this means I can develop faster and make changes faster than I could
if I was using the mapping files approach.
> How many others, not requested and even not needed, things you have using
> FNH's Automap ?
Not sure I understand the question...
> And how many others needed things you don't have using FNH's Automap ?
So far, I've been able to do everything I've needed to with pure
automapping. But I don't claim that automapping does everything you
can do in the mapping files.
In the cases where automapping can't do the job, you can write
additional mapping classes in C# ("Fluent Mapping"), or write your own
XML mapping files in the same way that NHibernate has always
supported.
I made the suggestion because Brad's problem seems simple enough to be
handled by automapping, and just wanted to make sure he was aware of
the option.
-Tom
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
