Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possibly a simple (read dumb) question. I am in design phase of a web application – standard Spring MVC and planning on using Spring DAO support (jdbctemplate – no hibernate & no ibatis etc).
I am currently modeling my data objects for the RDBMS. What is the best practise for data types? Let’s say my primary key of a table is Numeric – Do I model that in my object as Long or long? Any problem / advantage of one over another?
Gurus?
Long is nullable. So an object with a null id (in Java) can represent an object that is not (yet) persisted. You can explicitly configure Hibernate to treat it that way, and if you don’t use Hibernate, it’s still good practice to give you DAO methods a way of finding out whether a particular object is already in the database or not.