Activity for Norbolsa
-
Norbolsa posted a comment on ticket #457
It would be great if this was built into into the driver
-
Ok, We will have to live with this... From our application perspective we can't capture the exception alone as we are using a jdbc framework (Spring) and we don't have the control when setting the parameters. As you are going to modify the message to write the parameter index, could it be possible to append that is due to a datatruncation? So we can discrimine if it is a datatruncation or a true data type mismatch Thank you
-
Also you will need to update documentacion at IBM Knowledge Cente "Data truncation" Specifies whether truncation of character data generates attention notices and exceptions. When this property is "true", the following apply: Writing truncated character data to the database throws an exception Using truncated character data in a query posts an attention notice. When this property is "false", writing truncated data to the database or using such data in a query generates no exception or attention notice....
-
DataTruncation numeric range bad behaviour in query statement
-
The code above doesn't work allways
-
One possible fix is this: try { if (defaultSchema_!=null) { connection_.setSchema(defaultSchema_);...
-
The code above doesn't work
-
One possible fix is this: try { if (defaultSchema_!=null) { if (defaultSchema_.equals("*LIBL")...
-
AS400JDBCPooledConnection throws SQL0713 and writes in the joblog
1
