Hi.
Paul Dupuis via use-livecode wrote
> I believe you need to surround the placeholder with single quotes.
Doesn't work, my LC doesn't do the replacement:
> UPDATE `t_test` SET `Text` = ':11' WHERE `Nummer` = ':22';
and
> UPDATE `t_test` SET `Text` = :'11' WHERE `Nummer` = :'22';
are sent to the
I believe you need to surround the placeholder with single quotes.
>> put "UPDATE `t_test` SET `Text` = ':11' WHERE `Nummer` = ':22';" into StrSQL
Also you can lose the semicolon as LC will only execute one statement at a
time. You cannot string statements.
Bob S
> On May 15, 2019, at 06:46
Hi,
the notation for revExecuteSQL you mention only works with 1-digit numbers
(in my LC 6.7.10).
Named arrays and 2- or more digit entries don't work - LC doesn't translate
'em. You can easily check this with your favorite network sniffer:
> put "bText" into myArr[11]
> put "99" into myArr[22]
>
No because the array form uses a substitution method for SQL statements like
"custom = ':1'" the :1 being replaced by the contents of tArray [1] when the
SQL statement is assembled. I don't think you can use ":lattitude" in the
select statement, but that would be an SQL limitation not an LC one.
hello
when you use array with revExecuteSQL like :
revExecuteSQL, dbID, tSQL, "tarray"
can we use array wth keys as text and not number :
tarray["latitude"] vs tarray[1]
i’ve some bug with first syntax.
Thanks for your light !
___
use-livecode mailin
