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.
For instance, there’s an integer column in a database table.
Then in java model, it can be mapped both as primitive int and Integer.
My question is what’s difference between the int and Integer in this case? And performance concern?
Thanks!
I tend to avoid using primitives. This is especially true for the Id attribute. This makes it possible to detect a not yet set value by testing for
null. If using Java 5 or above, auto-boxing takes away the pain (and is not a performance concern). But also for other attributes. As pointed out by @skaffman, primitives are not suitable for nullable columns and I prefer the code to be as flexible as possible.