145
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Dec 2024
145 points (99.3% liked)
Programming
17748 readers
509 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
To clarify: I am saying that it is not "normal" that the type you get back out is not only not necessarily the type that you put in, but may be different depending on the value that you put in. Put another way, sqlite is strongly typed unless you mistakenly thought that type affinities by themselves made it be strictly typed, in which case it becomes neither strictly nor strictly typed.
I think one of them should be "strongly", but I understood your point.
Thinking back, I don't have the doc easily accessible (on phone), but I think the C API state the type you want to read. Like
get_int(smt, VALUE_INDEX, …), so at least in the C API, most of this should not be visible. Maybe only theSELECT 1 = '1'part (or others comparaison fully done in the SQL string)?