Today we're shipping a small but lovely upgrade to Flare: every query exception now comes with a SQL statement you can actually copy and run.
Here's what query exceptions used to look like:
Query exceptions in Flare have shown the executed SQL for years. Can you spot the problem? Those UUIDs are strings, so they need quotes. Paste this into your database client and you get a syntax error. Laravel builds the message that way on purpose (exception constructors have to stay cheap and safe), so the bindings go in raw.
We weren't happy with that. Flare is where you go to fix things fast, and a broken SQL string slows you down every time you hit one.
So we added a step in the newest laravel-flare client. Before the message is sent to Flare, we walk the bindings and format them properly:
Click, copy, paste, run. The way it should have always been.
Happy debugging!
Continue reading
Bringing Flare back to Laravel 10 and PHP 8.1
Flare now supports Laravel 10 and PHP 8.1 again, so older apps get performance monitoring and logs too. Here’s how we did it.
Ruben
Your Laravel routes can carry metadata now, and Flare shows it
Laravel added a new way to attach metadata to routes, and Flare now automatically shows it on errors and traces
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
