-
Notifications
You must be signed in to change notification settings - Fork 499
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
MySQL Driver - 64 Character Identifier Limit #1
Comments
@sethcenterbar Thanks! I've removed the prefix In other situation we can take your approach though I think we should avoid really long columns. |
ghost
added
the
bug
label
Nov 30, 2020
ghost
closed this as completed
Nov 30, 2020
This comment was marked as spam.
This comment was marked as spam.
yevgenypats
added a commit
that referenced
this issue
Nov 1, 2022
yevgenypats
added a commit
that referenced
this issue
Nov 17, 2022
yevgenypats
added a commit
that referenced
this issue
Nov 18, 2022
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I love the idea behind this project and think it will be incredibly useful for many organizations. I'm hoping to be a contributor here, so let me know how I can help!
When running the example.config.yml, ec2 instances attempts to create a column named 'capacity_reservation_target_capacity_reservation_resource_group_arn'.
MySQL has a 64 character limit for identifiers, so we should find a way to identify and compact names > 64 characters long when using the MySQL driver. For the sake of autocomplete and api similarity, I actually think simply taking the first 64 characters will be the best bet in most situations.
The text was updated successfully, but these errors were encountered: