The JDBC spec states that TINYINT should be mapped to either byte or
short - so the "default" is a bit ambiguous. Ibator maps TINYINT to
byte which is correct on some databases. You can override this either
with a , or with a custom JavaTypeResolver (as you've
done).
Ibator in Eclipse can only f
Hi all,
I think iBATOR is really great and this time I'm using the automatic java
fields creation from my database columns from the Eclipse plugin.
I'm using MySQL and I have the following problem:
- all my TINYINT columns are mapped to Byte java fields (I would prefer Integer
or Short)
Looking
