Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requiring character set to be specified [JDBC479] #518

Closed
firebird-issue-importer opened this issue Feb 14, 2017 · 7 comments
Closed

Requiring character set to be specified [JDBC479] #518

firebird-issue-importer opened this issue Feb 14, 2017 · 7 comments

Comments

@firebird-issue-importer

Submitted by: William L Thomson Jr (wltjr)

Is replaced by JDBC502

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.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 14, 2017

Commented by: William L Thomson Jr (wltjr)

Various attempts at trying to connect
https://groups.yahoo.com/neo/groups/firebird-java/conversations/messages/11262

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 14, 2017

Modified by: William L Thomson Jr (wltjr)

Component: JDBC driver [ 10053 ]

Version: Jaybird 2.2.12 [ 10781 ] =>

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 14, 2017

Modified by: William L Thomson Jr (wltjr)

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.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Mar 4, 2017

Commented by: @mrotteveel

See discussion linked in previous comment. The character set problem was resolved, the other problem identified in that discussion will be addressed by JDBC417

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Mar 4, 2017

Modified by: @mrotteveel

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

resolution: Cannot Reproduce [ 5 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 25, 2017

Modified by: @mrotteveel

Link: This issue is replaced by JDBC502 [ JDBC502 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 25, 2017

Commented by: @mrotteveel

After receiving several more complaints, and having been bitten a few times myself by the connection character set requirement, I have decided to remove the requirement in Jaybird 3.0.2, see JDBC502.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment