This repository has been archived by the owner on Mar 11, 2020. It is now read-only.
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.
Fixes #35
While patching this, I also noticed the
$max_index_length
value, and found some backstory on that191
character limit here and in the source code ofwp_get_db_schema()
here.Because we are changing the length of the
args
column now anyway, and will be logging a notice to warn developers of that, I figured it was a good idea to constrain its length to an indexable size instead of allowing data that is knowingly too long to be indexed, and therefore, non-performant, to be used.I also considered reducing the length doing the same for the
hook
, but have left that off for now even though the same argument applies.I don't think an update process is necessary for this column given we still have only tagged
1.0.0-beta
. The column can be updated manually on the few sites using this plugin already.