Le 09/02/2010 13:26, Peter Derwa a écrit :
hi Frederic,
what do you mean by code generation from the database?
btw, Datasets is out of the question :) Datasets is something for
people who are used to work with framework 1.1 in my eyes :)
everything will stay object oriented because it's just very clear what
the code is really doing and what data you are using for it.
I wouldn't suggest using Datasets in any case.
using lazy loading is a different way of programming I think, but in
my eyes it's still much more effective to keep lazy loading in mind
while programming.
Entity framework is still out of the question (but that will change
in .Net 4.0, since they will support the use of Services and POCO with
EF)
If you really want to keep the complete relational mapping the way it
should be with NHibernate, it's almost impossible to disable lazy
loading at that point because you could have category entities which
would be loaded with all stuff that is organized within that category.
that would be completely obsolete when you want to edit the category
itself.
if you are an architect, you probably have seen quite allot of
techniques to load data, and I bet not a single one of them is as easy
as NH or EF to use :)
development speed is growing at percentages that you can't imagine,
and especially when you have to maintain an application.
That's why we chose for NHibernate and WCF because EF is still just in
it's beginning process. however I expect allot of improvements in 4.0
Our dataAccessLayer will also be only used within local network, so we
don't need to worry about security or other controls that won't have
the capability of lazy loading.
So keeping the above in consideration, in my opinion, the lazy loading
is a very good idea when your developers know how to use the lazy
loaded relations, no?
and last of all, what is NHibernate Sharding? my mother language isn't
English so I don't really know the meaning of it.
And do you possibly have some more information about it? articles?
blogs?
Hey,
Nhibernate sharding is the port of the hibernate sharding project,
allowing to run hibernate against many databases. You should search for
it,and it willbe a good answer to your questions about persisting in
differents databases.
Bycode generation I mean : You build the database scheme, and from the
scheme, givien a certain tool or technique you create the class and/or
the nhibernate mapping.
Your vision of the datasets is quite perverted by the 'orm point of
view'. When it comes to transfer a table or the result of a given sql
query accross boundary, dataset is still the best solution (especially
if you are using mtom messaging or intend to create an xml flow).
Dataset are not only the RAD Solution for 1.1 users.
Nhibernate from fartoday is more mature than EF, exception made if you
consider that ghost pattern generalisation is a good thing.
The fact is that the volume problem you are facing today will be the
same with any ORM framework available today : controlling the size
ofyour object graph includes controlling the business role of your object.
The most common issue you will face using an ORM in a distributed
scenario is recursivness; and lazy loading is a technical answer, but
not the silvber bullet. Lazy loading is usefull in specific use cases.
If you need examples, just ask;,
C.U
Fred
--
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.
