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
I'm working with an OC4J app, and have placed the logging selection call just
before the call to build the SqlMapClient (though in this case it is the
selectJavaLogging() method which is being invoked).
If there's nowhere else obvious, perhaps you could put it in your servlet's
init() method?
Well I do have sequences defined for my each table which acts as a
primary key for my table now I want to use this generatedkey as a
foreign key in another table so now if I use my class attribute to have
this sequence id , then how can I get that key in java code , I am
assuming I can do in fo
