Ocean West Posted August 6, 2016 Share Posted August 6, 2016 I guess the script is written for backwards compatibility but if we could guarantee FMP15 Server/Client would the sync perform better if it was using the Truncate Table function? Even have it in a loop iterating thru table instead of having to switch context even, and reduce script steps. 1 Link to comment Share on other sites More sharing options...
Jesse Barnum Posted August 6, 2016 Share Posted August 6, 2016 There are very few cases in MirrorSync when we delete all the records on a device, and only during certain initial sync scenarios - so it would have no benefit for the vast majority of the time. Where were you thinking about using it? Link to comment Share on other sites More sharing options...
Ocean West Posted August 6, 2016 Author Share Posted August 6, 2016 No plans just scrolling thru the script saw the steps and just thought candidate for new function Link to comment Share on other sites More sharing options...
Mike Duncan Posted August 8, 2016 Share Posted August 8, 2016 For what it's worth, you get this behavior for free if all the requirements are met. FM does a quick check to see if it can do this to increase performance. That check involves looking for and open/locked records, any cascading deletes or dependencies in the schema, and if you are in a found set of all records. If all conditions are met, it will functionally truncate the table for you, saving a load of time 1 Link to comment Share on other sites More sharing options...
Jesse Barnum Posted August 8, 2016 Share Posted August 8, 2016 Good to know, thanks Mike Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 2817 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now