"revdberr, " as the returned value on *successful* postgres operations
Dr. Hawkins
dochawk at gmail.com
Tue May 14 13:03:59 EDT 2013
On Mon, May 13, 2013 at 7:11 PM, Mike Bonner <bonnmike at gmail.com> wrote:
> Are you adding the ; at the end of your sql strings? I'm pretty sure rev
> appends its own ; so the result would be an extra one. Which might make
> postgres a) do whatever you told it to, then b) return a confused error due
> to the second ;
>
> Try it without adding the ;
>
I took off the trailing semicolon:
BEGIN TRANSACTION;
UPDATE baggins_bilbo____001_sofa SET A = 'Ape guy', B = 'Sunday', C = '9
banana', D = '', usr= '', tstmp = NOW() WHERE uniq_sfky =7;
UPDATE dhbk_dtIdx SET lastOpened=NOW(), usr=' ' WHERE
dtStem='baggins_bilbo____001';
COMMIT
and still get the same message.
Livecode certainly isn't adding semicolon after every line--if I take out
the others, the UPDATE throws an error.
I've also seen the same issue with single transactions outside of BEGIN
blocks.
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
More information about the use-livecode
mailing list