laravel eloquent update four digit year could not be found

Thanks I was actually of investigating this after someone asked me about performance and that's completely true.

And we can still use a scope for that to make it easier to use (we'll also make it accept either a Carbon instance or a string) : So all in all, my final recommendation is to stick with Carbon to get the start and end of day. So in order for it to work you'd have to also use PDO's emulated prepared statements which is not the recommended way. For some reason that I can't figure out, the functional index is not used when using prepared statements.Functional indexes are only available on MySQL 8.0.13 and above.The theoretical solution to this is to create a functional index on DATE(created_at)in MySQL. Unfortunately anything that involves the DATE() function, either by using DB::raw() or Laravel's WhereDate() function won't be able to use that index because it contains the timestamp. If you create a simple index on the created_at column, the Carbon approach that uses ->startOfDay(), ->endOfDay() and ->between() will be a lot faster because it can leverage the index. Which opened a whole new can of worms I hadn't really anticipated (which Oliver also pointed out in the comments).Īll of the approaches above have about the same performance if you don't have any index on the created_at column, which is probably fine if you need to filter a few dozens or hundreds of models by date, but if you start working with a lot more than that you'll need to create an index and. Note : This was not part of the original article, and someone on Linkedin asked me 'what about performance'. Now that looks pretty good to me ! Unfortunately it might not be the fastest solution. Enter fullscreen mode Exit fullscreen mode

Laravel eloquent update four digit year could not be found