There's no best way to do things... There are only individually preferred ways and then tools / standards (mostly tools that have become standards) that support you in doing what you want. And then, there are success stories with every way, and that's what makes life interesting.
I wouldn't be too mad about layering in todays software world. JDBC itself is a layer on top of any arbitrary proprietary RDBMS communication protocol, which itself is again based on TCP/IP, which in turn is layered on top of other network layers. Then again, JDBC is very simple for good reasons: With its simplicity, arbitrary proprietary SQL is supported - for instance H2's MERGE statement. So using plain JDBC is perfectly OK. But the nature of JDBC makes you write repetitive code (and mistakes), a problem that is not addressed in JDBC for those reasons. That problem is supposed to be addressed in higher-level layers... (like TCP addresses problems that IP might cause, if used "standalone"). Typesafety and CRUD are problem not addresses by JDBC... -- You received this message because you are subscribed to the Google Groups "H2 Database" 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/h2-database?hl=en.
