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.

Sign up for GitHub

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

Jump to bottom

Problems with chars not strictly ASCII #26

Closed
ckunki opened this issue Dec 2, 2022 · 1 comment · Fixed by #27
Closed

Problems with chars not strictly ASCII #26

ckunki opened this issue Dec 2, 2022 · 1 comment · Fixed by #27
Assignees
@ckunki
Labels
bug Unwanted / harmful behavior

Comments

@ckunki
Copy link
Contributor

ckunki commented Dec 2, 2022

see also exasol/mysql-virtual-schema#26
@ckunki ckunki added the bug Unwanted / harmful behavior label Dec 2, 2022
@ckunki ckunki self-assigned this Dec 2, 2022
ckunki added a commit that referenced this issue Dec 2, 2022
@ckunki
#26: Enabled to use Oracle database with characters not strictly ASCII.
c27cc52
@ckunki ckunki mentioned this issue Dec 5, 2022
Merged
@ckunki ckunki closed this as completed in #27 Dec 5, 2022
ckunki added a commit that referenced this issue Dec 5, 2022
@ckunki
#26: Enabled to use Oracle database with characters not strictly ASCI…
f1e178e 
…I. (#27)

* #26: Enabled to use Oracle database with characters not strictly ASCII.
* updated exasol-testcontainers and excluded vulnerability
* Removed repository maven.exasol.com
@allipatev
Copy link
Contributor

@ckunki
Is it still planned to work on improving the IMPORT_DATA_TYPES='EXASOL_CALCULATED' regime?
I still don't believe that both Oracle and MySQL JDBC drivers have the same incriminated bug :)

@exaSR exaSR mentioned this issue Nov 18, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ckunki ckunki

Labels
bug Unwanted / harmful behavior
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#26: Enabled to use Oracle database with characters not strictly ASCII. exasol/oracle-virtual-schema
2 participants
@allipatev @ckunki