Changed varchar length TRIGGER_NAME from 80 to 200 #245
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
maheshwarigagan
approved these changes
Oct 15, 2018
|
this will not be backwards compatible? |
zemian
added a commit
to zemian/quartz
that referenced
this pull request
Feb 11, 2019
This was referenced Mar 8, 2021
This was referenced Mar 16, 2021
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.
After deploying quartz to a Sybase database the following error occured:
After researching I found out that tables_sybase.sql is using
TRIGGER_NAME varchar(80)instead ofTRIGGER_NAME varchar(200). Length should be equivalent to tables_mysql.sql.Thanks to @iDschepe figuring this out.