|
From: <jue...@we...> - 2004-03-23 22:12:59
|
Let's return 0, analogous to ResultSet.getInt; I'll fix this for 1.0 = final (which is otherwise ready, including all docs and readmes). =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von tho...@tr... Gesendet: Di 23.03.2004 22:47 An: spr...@li... Betreff: RE: [Springframework-developer] Getting ready for 1.0 final Found on minor quirk in the new JdbcTemlpate convenience methods. = queryForInt returns the following confusing exception when the query returns the = value NULL. org.springframework.dao.InvalidDataAccessApiUsageException: Result = object (db-type=3D"NUMBER" value=3D"null") is of type [java.math.BigDecimal] = and not of required type [java.lang.Number] We could either return 0 (like getInt() on the ResultSet would), or we = could throw an exception with a different message. What do you think? I don't think this is a big deal, so I would not delay the release for = 1.0. Thomas ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |