Long or long ????

[mia]

in my domain classes

shall i use Long or long to save long values ..

actually when i am trying to get the data from database and if the value returned is null then an exception is thrown..

if i am using String then its ok ... but i think thats not a good method ...

can any one help me what to do here ...

i have the same doubt with double values also ..

if i am using wrapper classes i think ineed to register custom editiors for that ?????

please help ...

thanx

[katentim]

shall i use Long or long to save long values

Long has the advantage of allowing nulls, which map to a null in the database, and also explicitly show whether the field has been bound to or not.

if i am using wrapper classes i think ineed to register custom editiors for that ?????

Depends if you need to customise behaviour (e.g. allow nulls). The existing CustomNumberEditor works for wrapper classes like Integer, Long, Float, Double.

[manifoldronin]

I would always use Long the wrapper class for the primary keys and other significant columns (significant in the sense that they participate in some control logic). Modern JVMs are typically fairly efficient in allocating/gc small objects, so the price in performance is generally acceptable considering the benefits as katentim pointed out.