I am not sure what DB you have. One way to store files within the DB is to use BLOB's (Binary Large Objects). Using a DB entry to a file name sets up an inherent data consistency synchronization problem. What happens if the file is deleted via normal file system command? The DB wouldn't know about that. I am unsure what your intent here is given that the DB file names may not match the actual directory structure.
Update:
One of first Perl programs that I wrote was source code scanner. We had an application that could say about 30-40K things per language. Builds were failing in system test due to "unimplemented prompt". My code scanned the source code and (a) made sure that any prompt file that could be played was there and (b) identified prompt files that could never be played. I had to spend some time one this, but it worked. I don't have the source code because it belongs to my employer at the time. Consider some kind of DB validation process.
In reply to Re: Avoiding duplicate filenames
by Marshall
in thread Avoiding duplicate filenames
by htmanning
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |