Has any thought been put into possibly adding the ability to the Torque
database schema to map specific database fields to different Java types,
perhaps supplying a conversion function? This would allow one to have the
torque generated classes more accurately model the "java view", even if the
database dosn't.
I see something like this
<table name="book" description="Book Table">
<column
name="onloan"
required="false"
primaryKey="false"
type="SMALLINT"
javaType="boolean"
conversionClass="org.me.SmallintBooleanConverter"
description="Book Id"/>
...
</table>
where the conversionClass would be optional, with a set of defined default
conversion classes.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
