How to handle null-values with the peer-class [2nd call]

["Jostkleigrewe, Heiner" <He...@gt-net.de>]

Hello,

the peer-classes map the database-column-types TINYINT, SMALLINT, INTEGER,
BIGINT and FLOAT to the simple java-types byte, short, int, long and double.
These types are not able to store null-values. The better alternative is to
use the wrapper classes Byte, Short ....

Who is able to change the peer-classes? Is there nobody in the whole wide
world who uses null-values ?

Heiner.Jostkleigrewe@gt-net.de 



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org

Re: How to handle null-values with the peer-class [2nd call]

[John McNally <jm...@collab.net>]

"Jostkleigrewe, Heiner" wrote:
> 
> Hello,
> 
> the peer-classes map the database-column-types TINYINT, SMALLINT, INTEGER,
> BIGINT and FLOAT to the simple java-types byte, short, int, long and double.
> These types are not able to store null-values. The better alternative is to
> use the wrapper classes Byte, Short ....
> 
> Who is able to change the peer-classes? 

You can.  It is one of my low priority todo's, which means it is not
going to get done until I actually need it.

>Is there nobody in the whole wide
> world who uses null-values ?

I am sure you are not alone.  There would be others who would benefit
from your fixing this shortcoming.

john mcnally

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org