So where is the problem?Let's see, you have a back-end storage. It stores imagines. The user has stored an image twice (a copy, perhaps). For whatever reason, filenames are remapped. (You aren't assuming the actual user is going to remember the random file names, are you?). The OP implements the suggestion to rehash based on content - making the backend merge the two files. The user, whatever front end he's using, still sees two files. He then decides to delete one of his copies. Or modify one (keeping the other copy as an original).
Oops.
Of course, maybe the OP's system doesn't work that way. We do not know. But I think it's really, really bad to give the OP an advice that may cause to data loss, and then, if it's pointed out, try to wiggle out of it by making assumptions on the OPs system.
In reply to Re^12: Renaming an image file
by JavaFan
in thread Renaming an image file
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |