Tuna Toksöz wrote:
> - Use LINQ2SQL and EF designer (before look the generated code is 
> better to go to the church)
>
> You are the man, Fabio!
He tries hard! :D
>
> I have to disagree on making life easier. I believe ORM relieves the 
> pain in application development. Thinking in entities instead of db 
> tables is a real joy!
>
> On Sat, Sep 20, 2008 at 8:36 PM, Fabio Maulo <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     The ORM don't make the developer's life much easier...
>     The target of ORM is : Think before in your entities and your
>     model, then think on how make it persistent.
>
>     The life of a developer is the life of a developer...
>
>     BTW you can try some other tool as:
>     - write all code needed by your self using ADO.NET <http://ADO.NET>
>     - Use LINQ2SQL designer (before look the generated code is better
>     to go to the church)
>     - EntityFramework
>     - Another commercial and no-commercial ORM tool
>     - Code generators
>     - MS application blocks
>
>     After that you can choose which is the better tool for your systems...
>
>     I don't know who said that ORM make the life of a developer much
>     easier... for that, an ORM, should find a way to deal with some of
>     mine customers, pay my taxes, deal with my wife, deal with my dog
>     and so on.
>
>     2008/9/20 ndotan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
>
>
>         Hey all,
>         I have a theoretical question.i fail to see how nhibernate
>         makes life
>         easy for me by mapping relations.
>
>         Every way i look at it, it seems that it poses more work to the
>         programmer.
>         for example taking directly from the documentation:
>
>         
> http://www.hibernate.org/hib_docs/nhibernate/html/example-parentchild.html
>
>         Parent p = (Parent) session.Load(typeof(Parent), pid);
>         Child c = new Child();
>         c.Parent = p;
>         p.Children.Add(c);
>         session.Save(c);
>
>         1. I need to maintain both edges of the link myself,
>         2. i need to worry about cascade action
>         3. i need to worry about the extra sql that is generated if i
>         do not
>         use inverse=true
>         4. i need to worry about when to use lazy loading.
>         5. in many to many relations, i need to worry twice as much.
>
>         so is the only advantage in the querying? and if so, i imagine
>         that
>         most of the queries would be done in HQL and i could just do a
>         join
>         for the relations by hand.
>
>
>         i feel im missing a point.
>
>         thanks.
>
>
>
>
>
>     -- 
>     Fabio Maulo
>
>
>
>
>
> -- 
> Tuna Toksöz
>
> Typos included to enhance the readers attention!
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to