The life cycle of the mapping is explained here
http://fabiomaulo.blogspot.com/2010/03/nhibernate-mappings-path.html
2010/3/30 Fabio Maulo
> The third...
> After BuildSessionFatory all mapping-metadata are compiled to persisters
> and you can throw the Configuration with its state.
>
> 2010/3/30
The third...
After BuildSessionFatory all mapping-metadata are compiled to persisters and
you can throw the Configuration with its state.
2010/3/30 Diego Mijelshon
> Fabio answered he first part, so I'll answer the second one:
>
> "Is the impact on performance only in startup? Or is it olso duri
Fabio answered he first part, so I'll answer the second one:
"Is the impact on performance only in startup? Or is it olso during CRUD
operations?"
Once the SessionFactory has been created, it doesn't matter how you
configured it.
Diego
On Tue, Mar 30, 2010 at 10:36, Visar Uruqi wrote:
> I
The time consuming is the deserialization of XML and not reflection (proved
by ConfORM, that does not generate XMLs).
2010/3/30 Visar Uruqi
> Is it true that if I specify details in the mapping xml file
> like for example the data-type of the property the length and othe
> constraints,
> would r
Is it true that if I specify details in the mapping xml file
like for example the data-type of the property the length and othe
constraints,
would result in a faster startup and better performance?
(I came to this idea when I enabled the log4net Logging library, and
got
a bunch of mapping and refl
