Hi All.
I'm using iBatis 3 beta 5 for Java 6 with ojdbc6.jar (Oracle 11g).
I got working simple mapper like this:
public interface RateMapper {
@Select("select rate from rate_table where rate_id = #{id}")
double getRate(int id);
}
Then I tried to disable cache for this statement:
Nope. Nothing technical. I just happen to hate checked exceptions. :-)
The original exception is always nested within the runtime one though, so
you have full access to everything you need.
There is a bit of placeholder code where I had intended to build a hierarchy
of exceptions, similar to S
Why does IBatis 3.0 throw IbatisException (RuntimeException) instead of
checked exceptions?
Is this a limitation now due to the dynamic nature of the generic typed
mapped statement classes? IbatisException doesn't even seem to wrap
SQLException, I see it wrapping the native exceptions from my
Thanks for sharing this. Once iBATIS 3 is GA I'm pretty sure springsource will
pick this up. So as soon as
iBATIS 3 is out of beta feel free to open a jira ticket on the spring jira (you
could even do it right now,
but I'm not sure if spring wants to include integration code with iBATIS 3
beeing
yes, iBATIS does trim newlines from the SQL statement itself. If you're
using $substring$ replacement style parameters, they'll get trimmed. The
solution (and a safer way to code this) is to use JDBC #parameters#.
Clinton
On Thu, Dec 3, 2009 at 11:22 AM, Ivan Bojer wrote:
> Hi folks,
>
> I am
Hi folks,
I am going crazy with this and I would appreciate any help or hint!
Here is the sample:
RadiusServersDAO serversDao = new RadiusServersDAOImpl(sqlMapper);
RadiusServers aServer = getServerCraft()...
String endline = System.getProperty("line.separator");
String adminSecret = "aaa"; //$
