Transaction-like copy/move directories: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(interwiki) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
When user | When a user moves one file TC does a good job: It checks the available space and if the operation is cancelled TC asks if it should delete the file. | ||
But | But if you move directories and choose cancel TC asks only if to delete the last file. | ||
Example: Move C:\Mp3\Singer1 to D:\Mp3 - when cancelled user can F8 on D:\Mp3\Singer1 - not NICE | |||
Example 2: | |||
Job 1: move C:\Mp3\Singer* to D:\Mp3 (background, space available) | Job 1: move C:\Mp3\Singer* to D:\Mp3 (background, space available) | ||
Job 2: move C:\Mp3\Group* to D:\Mp3 (background, space available before end of job 1...) | Job 2: move C:\Mp3\Group* to D:\Mp3 (background, space available before end of job 1...) | ||
So when user cancel job 2 its | So when user cancel job 2 its leaving a mess in D:\Mp3 and there is no space available on the disk for job 1... | ||
job 1... | |||
With transactional-like copy/move it will be nicer.. | With transactional-like copy/move it will be nicer.. | ||
| Line 12: | Line 12: | ||
I don't thing about full ACID transactions :) | I don't thing about full ACID transactions :) | ||
Someone, if can, pleas correct my English, pleas... | Someone, if can, pleas correct my English, pleas... | ||
{{backlink|Internal functions Ideas and suggestions|Internal functions}} | |||
{{de|Transaktionsartiges Kopieren/Bewegungen von Verzeichnissen}} | |||
Latest revision as of 21:21, 16 October 2005
When a user moves one file TC does a good job: It checks the available space and if the operation is cancelled TC asks if it should delete the file. But if you move directories and choose cancel TC asks only if to delete the last file.
Example: Move C:\Mp3\Singer1 to D:\Mp3 - when cancelled user can F8 on D:\Mp3\Singer1 - not NICE Example 2:
Job 1: move C:\Mp3\Singer* to D:\Mp3 (background, space available) Job 2: move C:\Mp3\Group* to D:\Mp3 (background, space available before end of job 1...)
So when user cancel job 2 its leaving a mess in D:\Mp3 and there is no space available on the disk for job 1...
With transactional-like copy/move it will be nicer..
I don't thing about full ACID transactions :) Someone, if can, pleas correct my English, pleas...
Back to Internal functions