Comments
3 comments
-
We're slightly reluctant to do this because a synchronization alters a database, which is something that can't be taken too lightly. Making it too easy for users to potentially trash their database is risky.
However, we recognise that for those who know what they're doing, or for those who are using databases that aren't critical, it requires a few clicks.
Can you suggest how we might come to a compromise here? What did you have in mind?
David Atkinson
Red Gate Software -
I can understand the risk involve with this.
Can you do this.
If you see user is performing this in a very frequently in short time period you can ask users this option -
We've certainly had ideas in this area before - we even had scary thoughts of making it possible to compare and synchronize at the point where you're choosing a project...
However, one idea that gained a bit more impetus was to allow the user to flag a project as eligible for "one-step" synchronization. So after going through the synch wizard once, you'd be able to set this flag on the last step. The next time you open the synch wizard for this project on the first step you could then choose between synching immediately, or stepping through the wizard to maybe change a setting or two.
During all of the user testing that we have run, we do find that people have a real trepidation about making mistakes so we do very much err on the side of caution. I'll certainly raise this again for discussion, but I can't promise anything for version 8.
Thanks for the feedback.
Add comment
Please sign in to leave a comment.
Instead, if there is a option saying fast syncronizing, it will take previous syncronizing option and do the syncronizing at once which will be faster