on 2016 May 27 11:50 AM
Mobilink Sync - I'd like to setup one table in my publication to be "upload-only". I will set the download_ scripts to be {ml_ignore} and only setup ML scripts for the upload_.
This upload-only table will continue to grow in size without download cursors to partition or delete the data. Is there a way to maintain this upload-only table by deleting rows older than 30 days for example (without having those deleted rows upload in the upload_delete sync)?
I'm pretty sure that the STOP/START SYNCHRONIZATION DELETE command will do exactly what you want.
I think the sample on the page even demonstrates deleting records older than a month, which isn't exactly 30 days, but is pretty close. 🙂
Please note the warnings on the page. They are there for a reason.
Warning #1: This command can be useful when making corrections to a remote database, but should be used with caution as it effectively disables MobiLink synchronization. You should only stop deletion logging temporarily.
Warning #2: The way in which UltraLite traces row states is unique. Be sure you understand the implication of deletes and row states.
Reg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A good way to think about this feature/statement is that while active it simply prevents the DELETE operations from synchronizing.
So, if you have a downloaded row, and delete it while STOP SYNC DELETE is active, it's deleted from the remote but MobiLink won't hear about the delete.
If you insert then (normally) delete a row on the remote without synchronizing, nothing will be synchronized for that row, of course.
If you insert a row then delete it while STOP SYNC DELETE is active and then synchronize, what happens? The remote will synchronize the insert, only.
User | Count |
---|---|
73 | |
10 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.