-
Notifications
You must be signed in to change notification settings - Fork 598
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
Prune command fails to delete records then using with mysql on planetscale #1410
Comments
But deletes for prunes are already chunked by 1000 items each so we never delete 100K records at once? So I don't understand how this is possible? https://github.com/laravel/telescope/blob/4.x/src/Storage/DatabaseEntriesRepository.php#L352 |
No, that's just a query builder instance. |
Okay I've found now where this is: telescope/src/Storage/DatabaseEntriesRepository.php Lines 367 to 368 in 8c6591a
We'd probably need to do a chunk to clear entries here. Would love a PR for this. |
Thank you for reporting this issue! As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub. If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team. Thank you! |
A PR was merged for this, thanks |
Telescope Version
4.17.2
Laravel Version
10.31.0
PHP Version
8.2
Database Driver & Version
MySQL on planet scale
Description
After changing db from MySQL to MySQL on planet scale command
php artisan telescope:prune
fails, then tabletelescope_entries
has more than 100k records. Planet scale has limits (https://planetscale.com/docs/reference/planetscale-system-limits) and one of them isPer-query rows returned, updated, or deleted
100k.Steps To Reproduce
telescope_entries
;php artisan telescope:prune
The text was updated successfully, but these errors were encountered: