It's actually quite simple to fix... just don't use primitives. :-) You can also make your own type handlers for string and integer that always yield some default value instead of null.
Clinton On Sat, Aug 9, 2008 at 4:08 PM, John Clash <[EMAIL PROTECTED]> wrote: > > Quite bad news for me :( > > I use nullValue as a convenient brief instrument to unify both null values > OR empty String to NULL in the database (e.g. when importing from Excel and > some cells are empty (that yields null) and some have empty strings). > Handling it in Java or SQL code would clutter it quite much. > > Can we expect some substitute for this in iBatis 3? > > Ondra > > > > Clinton Begin wrote: > > > > I recommend not using nullValue replacement. It's confusing and doesn't > > work the way most people would expect it to, quite the opposite actually. > > It's used to map nullable columns to non-nullable class members, like > int, > > long, double, boolean etc... > > > > It will not be available in iBATIS 3. > > > > Clinton > > > > -- > View this message in context: > http://www.nabble.com/inline-map-format%3A-empty-String-in-nullValue-tp18905940p18908933.html > Sent from the iBATIS - User - Java mailing list archive at Nabble.com. > >
