I think I saw in a previous message that you are using revDataFromQuery to execute the BEGIN/UPDATE statements? If so, I'd say there could be unexpected results since that function expects a SELECT statement and returns the result of it. Not saying it won't work but revExecuteSQL is what should really be used for anything other than SELECT statements.
Pete lcSQL Software <http://www.lcsql.com> On Tue, May 14, 2013 at 10:03 AM, Dr. Hawkins <doch...@gmail.com> wrote: > On Mon, May 13, 2013 at 7:11 PM, Mike Bonner <bonnm...@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 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
