|
Sean, on my mind there is a small problem. In _most_ cases there are really no problems, but in the worst case one can loose unique data. I will take a look, how do other databases solve this problem. May be renaming existing file to name.bak can be a good solution.
What about special file this is not a problem at all - it's trivial to distinguish it from regular file. To Sean Lean
>> So, I believe that this case were re-written to be a feature request Agree. To All As regards restore, the possibility to rewrite source database became more inaccessible since FB2, and I think, it makes sense to apply such policy for backup Best regards, Eugene |
|||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Minor
Gbak shouldn't rewrite backup file by default
There, though, I believe an invalid assumption in the issue reported -- the destination file does not need to be a real file but can be a system device/redirection. As such, the necessity to force the destination to not already exist is not appropriate.
So, I believe that this case were re-written to be a feature request, whereby a new command line switch (or use the same "-c" as currently available for the restore function) would be added to check if the destination already exists and abort if it does.