Bug 1944653
| Summary: | DROP TABLE doesn't raise error while dropping non-existing table in MariaDB 10.5.9 when OQGraph SE is loaded to the server | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Michal Schorm <mschorm> | |
| Component: | mariadb | Assignee: | Michal Schorm <mschorm> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Heger <jheger> | |
| Severity: | unspecified | Docs Contact: | Lenka Špačková <lkuprova> | |
| Priority: | unspecified | |||
| Version: | 8.4 | CC: | databases-maint, hhorak, jheger, ljavorsk, mmuzila, rhel-cs-apps-subsystem-qe, toneata | |
| Target Milestone: | rc | Keywords: | Rebase, Triaged, ZStream | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | https://jira.mariadb.org/browse/MDEV-25373 | |||
| Whiteboard: | Waiting on upstream fix | |||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
.`MariaDB 10.5` now warns about dropping a non-existent table when the `OQGraph` plug-in is enabled
Previously, when the `OQGraph` storage engine plug-in was loaded to the `MariaDB 10.5` server, `MariaDB` did not warn about dropping a non-existent table. In particular, when the user attempted to drop a non-existent table using the `DROP TABLE` or `DROP TABLE IF EXISTS` SQL commands, `MariaDB` neither returned an error message nor logged a warning. This bug has been fixed, and a warning is now shown in the described scenario.
|
Story Points: | --- | |
| Clone Of: | 1942526 | |||
| : | 2095290 (view as bug list) | Environment: | ||
| Last Closed: | 2022-10-19 13:37:42 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1942526, 2092314 | |||
| Bug Blocks: | 1947388, 2095290 | |||
|
Comment 5
Michal Schorm
2021-03-31 09:50:49 UTC
This issue is tracked on the MariaDB upstream: https://jira.mariadb.org/browse/MDEV-25373 |