fix: bucket naming length #1092
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
gfyrag
approved these changes
Jan 8, 2024
Dav-14
force-pushed
the
fix/ledger_search_path
branch
from
58d33b4
to
85a8c4c
Compare
Dav-14
force-pushed
the
fix/ledger_search_path
branch
from
85a8c4c
to
1fe5af3
Compare
Dav-14
force-pushed
the
fix/ledger_search_path
branch
2 times, most recently
from
89b3c9f
to
1b2585d
Compare
Dav-14
force-pushed
the
fix/ledger_search_path
branch
from
1b2585d
to
1c2663e
Compare
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bucket <-> Ledger, naming convention:
Actually:
=> They are not constraint by the 63bytes limits
Fixes ENG-456
https://www.postgresql.org/docs/current/limits.html