On Thu, 22 Dec 2011 00:51:51 +0100, Ricky Clarkson <ricky.clark...@gmail.com> wrote:

My current client dislikes Hibernate (not that I'm proposing it)
because most of their technical staff have DB experience more than
straight programming experience; even the Business Analysts can talk
in SQL.  They worry that if Hibernate does something they don't expect
they won't be able to make the tweaks they want to, or export the
queries to SQL to be able to run parts manually.

iBatis has been tabled as something that doesn't even attempt to hide
the underlying SQL.  I personally don't know the requirements for that
particular project yet so I'm not recommending anything, other than
not deciding on the technologies before at least saying what the
project is for.

With iBatis you're more in control and can be a reasonable choice. But these scenarios worry me at another level: if people are "reasoning in SQL" they won't be designing in OO. Which is not a problem, of course, if they are aware of what they are doing.

Same point for greenfield projects where people start first designing the database. I'm still seeing this because when you're acquainted in doing that for decades it's a strong habit, but indeed the database should be designed after the core.


--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
fabrizio.giud...@tidalwave.it
http://tidalwave.it - http://fabriziogiudici.it

--
You received this message because you are subscribed to the Google Groups "The Java 
Posse" group.
To post to this group, send email to javaposse@googlegroups.com.
To unsubscribe from this group, send email to 
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to