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

Improve CLOB handling in Oracle dialect #249

Closed
redcatbear opened this issue Aug 27, 2019 · 0 comments · Fixed by #253
Closed

Improve CLOB handling in Oracle dialect #249

redcatbear opened this issue Aug 27, 2019 · 0 comments · Fixed by #253
Assignees
Labels
feature Product feature

Comments

@redcatbear
Copy link
Collaborator

Situations

An Oracle CLOB can be up to 2,147,483,647 characters long. Exasol only supports 2,000,000 character long VARCHAR.

We need to ensure that CLOBs up to the maximum VARCHAR size are imported completely.

Bigger ones need to be truncated by the loader (not the Virtual Schema).

@redcatbear redcatbear self-assigned this Aug 27, 2019
@redcatbear redcatbear added the feature Product feature label Aug 27, 2019
redcatbear added a commit that referenced this issue Aug 28, 2019
AnastasiiaSergienko pushed a commit that referenced this issue Aug 28, 2019
* #98: Switched on SuppressWarning support for Eclipse.

* #249: Updated documentation.

* #249: Improved `CLOB` handling in Oracle dialect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant