Question

I have an PHP website which creates and stores HTML template files on server based on user input.one user can create many templates.So to store the template files and associate them with the DB record ,what I do is-

“templates” is the table which hold other information about the template such as who created it etc. with unique auto-increment id as template_id

for example –
if template id is 1001
I convert it to hex which is 03e9
Now I split the hex number into 03 & e9 (after two numbers) becomes folder and e9 becomes
file with some extension as “e9.tpl”

This is how I can find out template from the file system if I know the template ID.I dont need to separately store the path to the file.

is it a good approach ? any shortfalls of this approach ? is there any other approach better than this ?

What are the advantages / disadvantages of storing the path to file in the database itself ? for example to enable using different discs serving templates etc.?

Answer 1

Are you doing this because you are worried that you might run out of file entries/inodes in the directory? In ext3 the practical limit is somewhere around 100.000 files (and 32.000 dirs).

Creating a directory structure on the fly is better done using modulu as in $dir = $id % 1000 and then put the new template in that dir ($dir/$id.tpl). That strategy will create max 1000 dirs and you have thus made it possible to handle around 100.000.000 files.

I don’t see any reason for messing with hexadecimal values or substrings.