The purpose of uploadseparate is to avoid potentially having thousands of files in a single directory (I think at some point, too many files in a single directory can degrade filesystem performance). Note, the UUIDs (and therefore folder names) have nothing to do with new sessions -- instead, they are related to the filenames. Each uploaded file has as part of its new name the first 16 characters of a UUID. The first 2 of these characters are used to determine in which subfolder to place the file when uploadseparate is True. You will not get a new folder for every single file (or session), as once you start to get a large number of files, some will share the same first 2 characters of their UUID segment.
Anyway, if you don't want this behavior, don't use uploadseparate. If you just want to designate a single separate folder for the uploads of a given field, you can instead use the "uploadfolder" argument to specify a custom folder. Anthony On Friday, November 10, 2017 at 2:49:15 AM UTC-5, T.R.Rajkumar wrote: > > The uploadseparate creates folder sructure like > uploads/amc_master.annexure/a0, uploads/amc_master.annexure/87 for the > field annexure in table amc_master. Here a folder is created with the first > two letters of UUID. So for me each session a new UUID folder is created > and the annexure file is stored in it. This results in each UUID subfolder > storing just one file. I would like all the annexure files in > uploads/amc_master.annexure folder and not in UUID subfolder. How to do > that? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
