OK, well if that's really a problem, the only other way I can think of is calculate the timestamp in your LC script and hand it off to the update statement as a literal value instead of using NOW()
Pete lcSQL Software <http://www.lcsql.com> On Sun, Aug 11, 2013 at 4:57 PM, Dr. Hawkins <[email protected]> wrote: > On Sun, Aug 11, 2013 at 3:50 PM, Peter Haworth <[email protected]> wrote: > > On Sun, Aug 11, 2013 at 1:16 PM, Dr. Hawkins <[email protected]> wrote: > > > >> UPDATE myindex SET tmstmp=NOW() RETURNING tmstmp; > > > > > > Just do SELECT tmstmp FROM myIndedx right after the UPDATE and before the > > END.and get rid of the RETURNING clause > > That's what I'm doing right now--and trying to avoid. It gives me the > full latency lag twice, at several hundred milliseconds each! > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
