"The de-facto strategy for sucking data in and out of these databases is to use an O/R mapping tool."
I don't see that where I work; it's a JDBC world. I would suggest something like "Database Design for Mere Mortals" instead of this. Or, if you must have Java content, "Java Programming with Oracle SQLJ."
1102991079
Posted byAnonymous Userat
2004-12-13 09:24 PM
I agree. I think that O/R mapping is too much like EJB. If you have serious capacity issues, plain old JDBC, and a thorough understanding of the particluar database are a must.
For smaller systems, fine, take the advantage those tools give, but be aware that they are generalized tools. For many applications you can't substitute for detailed knowledge of the products you are using.
"The de-facto strategy for sucking data in and out of these databases is to use an O/R mapping tool."
I don't see that where I work; it's a JDBC world. I would suggest something like "Database Design for Mere Mortals" instead of this. Or, if you must have Java content, "Java Programming with Oracle SQLJ."
I agree. I think that O/R mapping is too much like EJB. If you have serious capacity issues, plain old JDBC, and a thorough understanding of the particluar database are a must. For smaller systems, fine, take the advantage those tools give, but be aware that they are generalized tools. For many applications you can't substitute for detailed knowledge of the products you are using.