I've seen a sqlite database with datetimes in three different formats in the same field, because different parts of the application I inherited had different ideas of how to write a datetime and sqlite accepts everything. It's only a string after all.
That's a mistake that the same bad developer couldn't have done with a PostgreSQL or a MySQL.
I understand that SQLite can store datetime in REAL type no problems, just on import one needs to convert the date strings properly. Of course, stuffing strings verbatim may work too, but that's about the robustness of the load process or the ETL pipeline.
That's a mistake that the same bad developer couldn't have done with a PostgreSQL or a MySQL.