Anomoly when storing empty values into SQLite integer fields

Mark Smith Mark_Smith at cpe.umanitoba.ca
Wed Feb 22 10:07:50 EST 2012


Peter, very cool. I'm going to have fun with that one. LC is very powerful at
times. Oh, and thanks for posting to the bug list. While it is possible that
RR will say this behavior conforms to a particular standard and you just
have to code for it (as you have below) its still way, way to much work for
a supposed high level rapid application development environment. My 2 cents
anyway.

Cheers,

-- Mark


Peter Haworth-2 wrote
> 
> Hi Mark,
> I think this may not be difficult.  Turns out you can use an array with
> numbered keys instead of a list of variables with revExecuteSQL, so here's
> some code ( completely untested)
> 
> put 1 into x
> put "UPDATE test SET " into mySQL
> repeat for each item myField in "One,Two,Three"
>    if field myField is not empty then
>       put myField & "=:" & x & comma after mySQL
>       put field myField into myArray[x]
>       add 1 to x
>    end if
> end repeat
> put space into char -1 of mySQL
> put "where ID=" & tID after mySQL
> revExecuteSQL gConnectID, mySQL, myArray
> 
> Shouldn't be too hard to generalise it as a command/function if necessary.
> 
> 


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




More information about the use-livecode mailing list