Menu
Community /Pin to ProfileBookmark
@NogDogSep 16.2021 — #For some reason I feel like using a distinct user ID seems better than splashing actual user names all over the file system. :)
As far as a separate folder for each product (or whatever?), one concern that pops to mind is making sure whatever you think the largest number of products are you might ever have to support does not exceed whatever the server's operating system restrictions are for the number of folders under the same parent folder. (I have no idea what those numbers might typically be, and maybe is so high that you don't need to worry, but still might be worth a bit of googling to be sure.)@NogDogSep 17.2021 — #
That could run into the same problem: could you have so many users submit photos such that you'd reach a folder limit?
The last time I dealt with anything vaguely like this (several years ago), I think I just dumped all the images in the same directory, used something like the PHP@Salvignol#1637136 Yeah, I think that's the more robust approach, especially if the intent/hope is to have lots of users/products/images/whatever -- for some undefined value of "lots". :) If, on the other hand, you expect those things to be limited in number (e.g. only "editor" users can post images or something), then maybe it's overkill. Plus, I'm biased, as my current job of several years has me down in the database weeds at some point pretty much every day.
Should I use UUIDs to identify data in my database
I’m working on a little project, and in order to store users images related to an article, I decided to create a folder on the sever with the path “uploads/images” and then, inside this images folder, every time a user uploads images tied to a product, a new folder is created inside image with his name and a generated ID number, thus resulting in a path like “uploads/images/jane___doe123456789”. Then I will only have to store the folder path in the database and I wouldn’t have to rename every single image posted by a user. However I wondered if I should be using UUIDs to generate the folder names or another way?
Sign in
to post a comment9 Comments(s) ↴
0
@NogDogSep 16.2021 — #For some reason I feel like using a distinct user ID seems better than splashing actual user names all over the file system. :) As far as a separate folder for each product (or whatever?), one concern that pops to mind is making sure whatever you think the largest number of products are you might ever have to support does not exceed whatever the server's operating system restrictions are for the number of folders under the same parent folder. (I have no idea what those numbers might typically be, and maybe is so high that you don't need to worry, but still might be worth a bit of googling to be sure.)
0
@NogDogSep 17.2021 — #>@Salvignol#1637129 So should I create a folder for each user
That could run into the same problem: could you have so many users submit photos such that you'd reach a folder limit?
The last time I dealt with anything vaguely like this (several years ago), I think I just dumped all the images in the same directory, used something like the PHP
uniqid()0
@NogDogSep 17.2021 — #