-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
do not forget DB table prefix with truncate query #31620
Conversation
blizzz
commented
Mar 18, 2022
- as used in LDAP's AbstractMapping::clear() method
- and in Comment's ManagerTest::setUp()
- fixes a DB Exception with Oracle
- as used in LDAP's AbstractMapping::clear() method - and in Comment's ManagerTest::setUp() - fixes a DB Exception with Oracle Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
How does one know when PREFIX is needed and when not? |
It is not needed when using the query builder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That doc block thou 🤪
Maybe we fix that properly?
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
/backport to stable21 |
/backport to stable20 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
The backport to stable20 failed. Please do this backport manually. |
The backport to stable21 failed. Please do this backport manually. |
/backport to stable23 |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
/backport to stable22 |
/backport to stable21 |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
/backport to stable20 |
The backport to stable20 failed. Please do this backport manually. |