Database development
in [Java Programming]
|
Prev: Null pointer issues
Next: Urgent
From: Pitch on 29 Apr 2010 11:25 In article <4bd8e72a$0$277$14726298(a)news.sunsite.dk>, arne(a)vajhoej.dk says... > > On 28-04-2010 04:52, Pitch wrote: > > In article<4bd79011$0$284$14726298(a)news.sunsite.dk>, arne(a)vajhoej.dk > > says... > >> On 27-04-2010 04:54, Pitch wrote: > >>> In article<hr3r1v$bvp$2(a)news.albasani.net>, noone(a)lewscanon.com says... > >>>> junw2000(a)gmail.com says... > >>>>>> When I work on database development projects, I use JDBC and SQL. Many > >>>>>> people use hibernate/spring. Can somebody explain the pros and cons of > >>>>>> using JDBC and SQL vs using hibernate/spring on database > >>>>>> developments? > >>>> > >>>> Pitch wrote: > >>>>> I always believed that ORM systems are forcing you to write your own > >>>>> business-rules layer apart from the persistence layer. That way database > >>>>> access is kept simple and easy mantainable. > >>>> > >>>> ORM doesn't force business rules into a separate layer and raw JDBC calls > >>>> don't force them into the same layer as persistence. > >>> > >>> I disagree. > >> > >> Can you explain what prevents you from copying business logic and > >> for that matter presentation logic into Hibernate/JPA data classes? > > > > experience > > Well - ORM implementations does not carry experience AI into the > app. > > And your experience is not part of the ORM. :) Well, arent' you a nitpicker. Are you and Lew the same person? -- stirr your cofee properly |