Anomoly when storing empty values into SQLite integer fields

[Mark Smith]

slylabs13 wrote
> 
> It may be a small distinction, but NULL is ASCII 0. An empty string is
> nothing at all, so far as I know. To a human this is splitting hairs, but
> to a computer all hairs must be split. 
> 
> 

The scenario seems to be (1) if you create a new empty record all the
undefined values are null. (2) If you try to store an undefined field (LC
field), LC puts an empty string. It does this for any SQLite field type. (3)
When you read it back, if the SQlite field  is an integer LC displays a
zero, if the SQLite field is text, then LC leaves it as an empty string. 

--
View this message in context: http://runtime-revolution.278305.n4.nabble.com/Anomoly-when-storing-empty-values-into-SQLite-integer-fields-tp4408942p4412919.html
Sent from the Revolution - User mailing list archive at Nabble.com.