When running tests of entities or other code on mysql vs. sqlite one expects reasonably consistent results.
Drupal code in the mysql driver sets the STRICT_ALL_TABLES mode so that inserting an over-long string into a VARCHAR field is an error
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-strict
However, the sqlite driver does not add any column constraints on with a CHECK statement on those columns so a value that would cause a database exception on mysql will work on sqlite becuase any length string is saved as the expected behavior (see https://www.sqlite.org/faq.html).
Run a kernel test on mysql and sqlite with an entity type with a field with a 40 char limit. Insert 100 char string - notice that it works on sqlite, fails on mysql.
sqlite should enforce VARCHAR column lengths with a CHECK constraint.
patch + tests
n/a
n/a
Newly created sqlite tables will enforce VARCHAR lengths.
todo
Needs work
11.0 🔥
sqlite db driver
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
+1 and I'd raised priority as it will help wasm previews
Please read comments and open tags before putting into review
Well, it has a MR now, but looks like not even code style is passing.