mirror of
https://github.com/fleetdm/fleet
synced 2026-05-18 06:28:40 +00:00
0b7167b37c
Fixes #28573 Fixes #31141 I don't know of a good way to add automated tests for this unfortunately - there is no easy way that I can see in our tests to really reproduce either of these issues Manual testing can be done for 31141 by creating a different user, recreating the nano_view_queue as that user using the old query(i.e. without SQL SECURITY INVOKER), and then deleting the user, seeing that the nano_view_queue gets busted(i.e. no queries can be run against it), then doing this migration or even just running the new query and verifying that the nano_view_queue can be queried again. # Checklist for submitter If some of the following don't apply, delete the relevant line. ## Testing - [x] QA'd all new/changed functionality manually ## Database migrations - [x] Checked table schema to confirm autoupdate - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). |
||
|---|---|---|
| .. | ||
| cached_mysql | ||
| filesystem | ||
| mysql | ||
| mysqlredis | ||
| redis | ||
| s3 | ||