We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An Oracle CLOB can be up to 2,147,483,647 characters long. Exasol only supports 2,000,000 character long VARCHAR.
CLOB
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).
The text was updated successfully, but these errors were encountered:
#249: Updated documentation.
c495513
Task-Url: #249
#249: Improved CLOB handling in Oracle dialect.
b490d31
Feature/249 improve clob handling in oracle dialect (#253)
f400760
* #98: Switched on SuppressWarning support for Eclipse. * #249: Updated documentation. * #249: Improved `CLOB` handling in Oracle dialect.
redcatbear
Successfully merging a pull request may close this issue.
Situations
An Oracle
CLOB
can be up to 2,147,483,647 characters long. Exasol only supports 2,000,000 character longVARCHAR
.We need to ensure that
CLOB
s up to the maximumVARCHAR
size are imported completely.Bigger ones need to be truncated by the loader (not the Virtual Schema).
The text was updated successfully, but these errors were encountered: