[MDEV-31092] mysqldump --force doesn't ignore error as it should Created: 2023-04-20 Updated: 2023-07-31 Resolved: 2023-07-31 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.6.12, 10.5 |
| Fix Version/s: | 10.4.31, 10.5.22, 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2, 11.2.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Susmeet Khaire | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | mysqldump | ||
| Description |
|
Customer has few legacy functions. One of the function has some syntax error.
Force option is supposed to ignore the error, add a comment in the dump file and move on to the next object. |
| Comments |
| Comment by Daniel Black [ 2023-04-21 ] | ||||||||||||||||||
|
reproduced with:
I suppose it would be more consistent to treat events and triggers the same way during mariadb-dump too. | ||||||||||||||||||
| Comment by Daniel Black [ 2023-04-21 ] | ||||||||||||||||||
|
It occurs to me we could just removing the validation of the function in SHOW CREATE FUNCTION? This would make it equivalent to triggers and events who's SHOW SQL doesn't validate the function. Any recommendation serg? | ||||||||||||||||||
| Comment by Sergei Golubchik [ 2023-04-24 ] | ||||||||||||||||||
|
danblack, I think just making --force to continue over errors should be enough here. If someone would want to include invalid routines into the dump it could be easily achieved by dumping mysql.proc and not using --routines |