How do you modify the timestamp in local mode, or what constitutes a change that you would change the local and not update the backend instead?
On Wed, Jul 12, 2017 at 12:51 PM, < [email protected]> wrote: > VFP9SP2 app, MySQL(MariaDB) secure database on web > > Scenario: customer uses my software but has an extremely slow connection > to the remote database and as such, queries involving large, > sometimes-changing lookup data is slow. > Solution: pull data locally for quick lookup. This works if I can do > some sort of Sync operation to make sure the local copy matches the remote > copy. > > The Primary Keys are varchar-40 GUID, and there's a timestamp field as > well. My thought was to use those 2 fields for the sync. If it exists in > both and the remote timestamp is newer, update the local record. If it > exists in the remote but not locally, add it local. If it exists in the > local but not in the remote, delete it from local. Any new adds or updates > to existing records will then be done to the remote database and then > echoed locally. > > I was thinking I'd setup MariaDB locally for this local database. > > Comments on that plan of attack? > > tia, > --Mike > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYL5zEbbHYWg_gdU9TWAjvhjZ=xtkmrhz6t+rrf5+v6...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
