It's a great big object oriented world out there :) Also... primitives can't be null but database columns can be null.
Abator's default behavior is to use objects, but you can force a primitive with a <columnOverride> if you want to. Jeff Butler On 4/6/07, Mark Volkmann <[EMAIL PROTECTED]> wrote:
It seems that by default Abator-generated model classes use type wrappers instead of primitive types for fields that correspond to database table columns. For example, a table with a column of type int will have a corresponding model object field of type Integer. Why aren't primitive types used? Can Abator be configured to use primitive types?
