Component: JDBC driver [ 10053 ]

Version: Jaybird 2.2.12 [ 10781 ] =>

description: I am VERY displeased that all new versions are requiring a character set to be set. This has broken just about every Java application where I am using JayBird. Which I have been using it for over a decade!!!! I am VERY displeased with this breakage and the driver should work out of the box as it used to before without having a character set specified. I wasted HOURS trying to get this to work with 3.x. It is completely unacceptable to have made this change to 2.x as well. There is no reason for this. Things worked fine, and now they are broken. The guides as to how to set this do not work. I have not been able to do this via Tomcat DBCP pool, nor via direct usage.

Revert what ever you did that created this problem. I have my environment setup properly. Java has no problem detecting system locale on any of my systems. There is no need to be setting this in another place. I have NEVER had an issue with JayBird till now. I can understand making a change to say 3.x, But this should never have changed 2.x. Your BREAKING existing applications for no good reason. Stop this and revert this immediately!

=>

I am VERY displeased that all new versions are requiring a character set to be set. I wasted HOURS trying to get this to work with 3.x. The guides as to how to set this do not work. I have not been able to do this via Tomcat DBCP pool, nor via direct usage.

status: Open [ 1 ] => Closed [ 6 ]

resolution: Cannot Reproduce [ 5 ]

Link: This issue is replaced by JDBC502 [ JDBC502 ]