Differences
This shows you the differences between the selected revisions of the page.
| 2005-04-14 | 2005-04-22 | ||
| 500 limit (martin) | task_rename (martin) | ||
| Line 18: | Line 18: | ||
| * Before using the function make sure that WinSCP knows correct timestamps of remote files, to avoid losing data. | * Before using the function make sure that WinSCP knows correct timestamps of remote files, to avoid losing data. | ||
| * WinSCP will detect that **something** has changed in the directory only. It won't know what has changed actually. So it must perform full synchronisation of that directory. As a result it may not upload only the file changed just at the moment, but any file that is out of sync. In other words, you should start the //Keep remote directory up to date// function only, when the selected local and remote directories are completely (or almost completely) [[task_synchronize_full|synchronised]]. | * WinSCP will detect that **something** has changed in the directory only. It won't know what has changed actually. So it must perform full synchronisation of that directory. As a result it may not upload only the file changed just at the moment, but any file that is out of sync. In other words, you should start the //Keep remote directory up to date// function only, when the selected local and remote directories are completely (or almost completely) [[task_synchronize_full|synchronised]]. | ||
| - | * When you rename file or directory, WinSCP will see it as removal of one file and addition of another and it will reflect the change on remote directory as such. So it is not recommended to use the function to "rename" large files and directories. You should better do this manually. | + | * When you rename file or directory, WinSCP will see it as removal of one file and addition of another and it will reflect the change on remote directory as such. So it is not recommended to use the function to "rename" large files and directories. You should better do this [[task_rename|manually]]. |