|
From: <tri...@tr...> - 2004-02-25 13:20:14
|
I can't see any reason for using a prepared stetement rather than a statement if there aren't any bind parameters. I'm OK with changing this to a Statement.executeUpdate(sql). Thomas Quoting "jürgen höller [werk3AT]" <jue...@we...>: > Thomas, everybody, > > Any reason why JdbcTemplate's update(sql) method uses a > PreparedStatement without bind parameters? To be consistent with the > query methods that take static SQL, update(sql) should really use a > plain Statement... > > BTW, Keith and me are currently refining the use of native JDBC > extraction in JdbcTemplate: This just makes sense when application code > will touch - and potentially cast - JDBC objects like PreparedStatements > or ResultSets. Thus, it isn't necessary for execute(sql) or update(sql). > > Juergen > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |