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

Put the connection charset in sqlscale of blobs when appropriate [CORE1332] #1751

Closed
firebird-issue-importer opened this issue Jun 28, 2007 · 4 comments

Comments

@firebird-issue-importer

Submitted by: @asfernandes

Different of what is documented, sqlscale of blobs is always using the blob charset.
It should be consitent with strings, i.e., it should be the connection charset if the connection charset is not none and the blob charset is not none/octets.

Commits: 410b280

====== Test Details ======

Sent feature request to dimitr, forwarded it to Alex (about displaying blob character set in SQLDA output), letter 26-may-2015 14:37

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 28, 2007

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 26, 2007

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

Workflow: jira [ 12450 ] => Firebird [ 15335 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 26, 2015

Modified by: @pavel-zotov

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

QA Status: Not enough information

Test Details: Sent feature request to dimitr, forwarded it to Alex (about displaying blob character set in SQLDA output), letter 26-may-2015 14:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants