Skip to content

Set the varchar2 type length to be "CHAR" instead of the default "BYTE" #12848

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

Merged
merged 1 commit into from
Aug 1, 2025

Conversation

fechen123
Copy link
Contributor

What does this PR do?

To fix the error "ORA-12899: value too large for column ..." when loading vector data to DB.

What are related issues/pull requests?

N/A

Tasklist

  • AI (Copilot or something similar) supported my development of this PR
  • Make sure code is correctly formatted (cf pre-commit configuration)
  • Add test case(s)
  • Add documentation
  • Updated Python API documentation (swig/include/python/docs/)
  • Review
  • Adjust for comments
  • All CI builds and checks have passed
  • ADD YOUR TASKS HERE

Environment

Provide environment details, if relevant:

  • OS:
  • Compiler:

to fix the error  "ORA-12899: value too large for column ..." when
loading vector data to DB.
@rouault rouault added the backport release/3.11 Backport to release/3.11 branch label Aug 1, 2025
@rouault rouault merged commit e36c6fa into OSGeo:master Aug 1, 2025
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/3.11 Backport to release/3.11 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants