4 ms·
I had no idea SQLite was so fluid with its column types - that's kind of alarming. I guess it's fine if you still have an ORM in between you and it, and this S
by goodells 5y ago
I had no idea SQLite was so fluid with its column types - that's kind of alarming. I guess it's fine if you still have an ORM in between you and it, and this STRICT syntax is probably the most reasonable workaround, but it just seems like a band-aid on top of not following the sensible pattern of every other database engine.
- rastapasta42 5y agoI find in practice this limitation is not an issue and column flexibility does not get in the way.
- temp8964 5y agoThe problem is not it does not get in the way. The problem is that some expect it to get in the way when the data is not right and assume it will do when in fact it won’t .
- chousuke 5y agoThat's kind of the problem. The database absolutely should get in your way if you try to put nonsense data in it. For the kinds of uses SQLite sees, the loose approach to data integrity may not have caused much grief, but I can't imagine many situations where it would have helped either. Having support for enabling sane behaviour is welcome even if it has to be opt-in for compatibility.
- kevin_thibedeau 5y agoIt's designed to integrate with Tcl with minimal fuss over typing. The world latched on to it because of its dependability and relative light weight.