@jessethanley@PlanetScale I haven’t had connection issues either, but am curious to see if it improves response time.
That’s a good little Sunday project
@jessethanley@PlanetScale@MostlyTechPod Great episode, glad to hear that pain is behind you. Curious to hear if the rest of your stack ends up leaving Heroku too
@_swanson Would love to hear more about this move, been working towards the same. Had a few issues with Heroku recently with replicas falling behind or crashing and it’s hard to diagnose/fix. Hopeful Planetscale will be an upgrade
📺 Here is What's New in Laravel 13.6
➡️ Debounceable queued jobs
➡️ JSON health route responses
➡️ Cloudflare Email Service support
Thank you Matthew, @wendell_adriel & @dwightconrad 🙏
@deinstinct@_newtonjob If that’s the case maybe create a Ban record where its created_at gives you the banned_at time. Plus you can keep a record of bans
@_newtonjob Don't quite know if I'm ready to try that in Laravel - it's a very Rails-y approach. But it's cool, something different. Lots of small models instead of filling up one model with nullable columns
@_newtonjob There was the argument too that you wouldn't need to add an index on a received_at timestamp, that you get an index for "free" because of the order_id index on the new table