fix: support longer index and table names - #51593
Merged
Merged
Conversation
susnux
added
2. developing
susnux
force-pushed
the
chore/support-longer-names
branch
4 times, most recently
from
March 20, 2025 08:57
1d770b0 to
98d731d
Compare
susnux
marked this pull request as ready for review
March 20, 2025 08:58
susnux
requested review from
artonge,
nickvergessen,
provokateurin and
yemkareems
and removed request for
a team
March 20, 2025 08:58
susnux
added
3. to review
nickvergessen
previously requested changes
Mar 24, 2025
nickvergessen
left a comment
nickvergessen
left a comment
Member
There was a problem hiding this comment.
11g is still supported and that is actually what all apps tests against atm iirc.
This was referenced Aug 22, 2025
Merged
Merged
Merged
Merged
Merged
This was referenced Sep 25, 2025
Merged
Merged
susnux
force-pushed
the
chore/support-longer-names
branch
2 times, most recently
from
November 27, 2025 17:46
ac7b43c to
2c0ddb1
Compare
susnux
requested review from
CarlSchwan and
nickvergessen
and removed request for
artonge
November 27, 2025 17:46
Contributor
Author
|
Oracle 11 is no longer supported. |
susnux
dismissed
nickvergessen’s stale review
November 27, 2025 17:47
Oracle 11 is no longer supported.
susnux
commented
Dec 1, 2025
susnux
force-pushed
the
chore/support-longer-names
branch
from
December 1, 2025 13:52
e259521 to
fcc89e2
Compare
14 tasks
provokateurin
approved these changes
Dec 8, 2025
Merged
CarlSchwan
approved these changes
Jan 16, 2026
We do not support Oracle 11 anymore but at least Oracle 12c (12.2). So the limitation is gone (Oracle now supports up to 128 character long names). Instead we are now limited by MySQL (64 characters) and PostgreSQL (63 characters). Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
susnux
force-pushed
the
chore/support-longer-names
branch
from
January 18, 2026 13:50
fcc89e2 to
67eef32
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
If Oracle is not explicitly disabled by an app we check the table names / key names / column names for legacy Oracle length of max. 30 characters.
But since Oracle 12c the limit was increased to 128 characters.
So nowadays we are limited by MySQL / Mariadb and Postgres:
This PR adjusts the checks to only check for Oracle specific behavior but limit the name length to 63.
Checklist