[10.x] Fix issue with table prefix duplication in DatabaseTruncation trait #48291
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.
This pull request addresses the issue documented in #48264
where the DatabaseTruncation trait would attempt to truncate a table with a prefix being applied twice when using a DB connection configured to prefix all tables.
Changes Made:
removeTablePrefix
to remove the table prefix from a table name if it exists.truncateTablesForConnection
method to utilizeremoveTablePrefix
when checking for table existence and performing truncation.Steps to Reproduce:
Expected Outcome:
Additional Context:
Testing: