Prefer strict tables in SQLite
evanhahn.com
Prefer strict tables in SQLite
1–10 of 188 posts
Re: Prefer strict tables in SQLite
#2It really should be default, but it isn't due to backward compatibility (i assume).
Re: Prefer strict tables in SQLite
#3It really should be default, but it isn't due to backward compatibility (i assume).
It’s a stated [0] goal of the project:
> SQLite strives to be flexible regarding the datatype of the content that it stores.
Re: Prefer strict tables in SQLite
#4It really should be default, but it isn't due to backward compatibility (i assume).
I’m kind of curious why the decision to have implicit casting like this was made in the first place. I can’t think of a single upside other than not having to type out cast(foo as bar)
Re: Prefer strict tables in SQLite
#5I would’ve thought this was the default.
Re: Prefer strict tables in SQLite
#6It really should be default, but it isn't due to backward compatibility (i assume).
I’m kind of curious why the decision to have implicit casting like this was made in the first place. I can’t think of a single upside other than not having to type out cast(foo as bar)
IIRC, the project started out as TCL code and it carried that vibe through to what it is today.
Re: Prefer strict tables in SQLite
#7It really should be default, but it isn't due to backward compatibility (i assume).
I’m kind of curious why the decision to have implicit casting like this was made in the first place. I can’t think of a single upside other than not having to type out cast(foo as bar)
SQLite docs: The Advantages Of Flexible Typing: https://sqlite.org/flextypegood.html
Re: Prefer strict tables in SQLite
#8about the use of ANY, that's perfect for tracking changes on an audit table per field
Re: Prefer strict tables in SQLite
#9I'd like to see STRICT as the default.
That's pretty much the only disagreement with the SQLite developer, who is an amazing guy that wrote an amazing tool!
Re: Prefer strict tables in SQLite
#10really interesting, thanks