You are always welcome. SQLite is not strongly typed - you are very welcome to store an integer in a text field (in fact it results in only using the data associated with the smallest integer internal type that can hold the value, so a clear advantage in the embedded world). You are also welcome to put a string or blob into an integer field.
You can check the value of a type using the typeof(col) SQL function in a query - different rows may indeed hold differently typed values for the same column. You can add a check constraint to a column you wish not to contain a value that isn't of an exact type. That's the very very short version, there are many caveats and things to note and the best place to do so is at: https://www.sqlite.org/datatype3.html Hope that helps! Ryan On 2015-04-09 07:04 PM, Gustav Melno wrote: > Thanks for the help. Adding a trailing underscore helped also. I'm > still wondering why insertion worked at all because defining oid as > column name with the type VARCHAR should result in an error on execution.
