Anomoly when storing empty values into SQLite integer fields
bobs at twft.com
Thu Feb 23 13:45:49 CST 2012
Using numToChar(0) from within LC puts NULL into the column. I hope that clears it up a bit more.
On Feb 23, 2012, at 10:08 AM, Mark Wieder wrote:
> Bob Sneidar <bobs at ...> writes:
>> I just tested this with a numeric column in mySQL. The column has NOT NULL
> unchecked and the default value set
>> to NULL. When I updated from LC setting the column to NULL that is the value
> that the column was set to.
>> HOWEVER if I updated the column with an empty string, I got 0 just as you say.
> We good so far? Okay.
>> So I wanted to see what would happen if I bypassed LC altogether and did the
> same updates in a mySQL utility. I
>> got THE EXACT SAME RESULTS!!! When I updated a numeric column with an empty
> string, I got the number 0. What
>> does this all mean? It means that LC is NOT borking the update. It is just the
> way SQL reacts when you send an
>> empty string to a numeric field!
>> They only real issue left is that LC converts a NULL value to an empty string
> in it's queries for the reason I
>> explained, that LC abhors an ASCII 0 in a string. I hope I have made this
> clear now. I have screen snapshots to
>> verify my results if you would like me to send them to you off list.
> What happens if you use numtochar(0) instead of NULL or an empty string?
> Mark Wieder
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode