a bit of controversy for Monday , to get you going <a href="https://www.youtube.com/watch?v=ij5vpL9YDEc" target="_blank" rel="noopener nofollow">video here</a> this is obvioosly a bigger question than the title lends to… , the argument is , use datetime, there are many uses of a boolean that can not be modelled properly by a datetime , some things are truly binary true / false that doesn’t depend on known time and don’t stay that way

Welcome to Laravel Dev! It's a cozy corner for all things Laravel. Share, learn, and explore the Laravel universe. Upvote or downvote, after reading, it's essential

Laravel Dev

Argues against using boolean fields in databases, suggesting datetime fields as a better alternative for tracking state changes. The post acknowledges this is a controversial stance and notes that some truly binary conditions may still require boolean representation, but emphasizes that many boolean use cases can be better modeled with temporal data that captures when changes occurred.

You should stop using booleans in your database

This is a very silly video to say the least. To use a datetime instead of boolean? That is simply WTF. Like in his example, a simple todo app, having Done as a datetime is fine, unless you want to toggle it. A better option would be to use a byte or even int as Done, and have a datetime for UpdatedAt, or have another log table for simply events which you then have a one to many relations.
Using a byte or even int is perhaps better than a boolean, you either have 0 or anything that isn’t zero. Having a datetime for fields like IsDeleted, IsHidden and many other cases is simply stupid, because if you want to make the record IsHidden = 0, you need to set the value to NULL which is always a gymnastic operation on best of days, indexes go nuts over such.
I always see videos like this with titles like “Never do this …”, “Why I stopped doing this”, “Never use … whatever”. Theo GG does this for all his videos basically, which is why I blocked him. Those videos are always nonsensical. At best they talk about a very extreme case which you basically will never get into.
This is just a video to scare you or make you uncomfortable. This video is quite silly, stupid even and his case is so weak. This is at best just a nonsense clickbait video.

Does “You should stop using booleans in your database” mean we should use char data type with ‘Y’ or ‘N’ constraint?

while I have advocated for this for a long time, databases struggle with indexing and querying when most rows have it NULL.
Nowadays I use a combo od datetime field + autogenerated column that is boolean purely for queries that test if something was done, not when

DateTime instead of boolean? WTF? You either need one or the other. Which one you need is defined by the requirements that you have. If you don’t know what the requirements are, you are either making the second step before the first (i .e., when you are a single developer), or should throw this back to the person who wrote down the requirements (if you work in a team/company) and tell them to do their job right the next time.