Thanks, Massimo. I wasn't aware of that. Looks like I should start changing certain fields to "uploadseparate = True" rather than the other way around.
However, as I mentioned, in the demo mentioned in this thread, when files are deleted, the folders that used to contain them remain. Is this a feature specific to this demo, or is this generally the case when using "uploadseparate = True"? If it's the latter, is there some automatic way for those folders to be deleted when their corresponding files are deleted? On Saturday, August 9, 2014 11:53:04 AM UTC-5, Massimo Di Pierro wrote: > > uploadseparate makes sure that if you have many uploads they are stored in > different (sub)folders. This is important for speed because if you have > more than 1000 files in a folder accessing the file system is a bottle > neck. This does not affect the demo but it is good practice to use > uploadseparate. It should have been the default option but it is not for > backward compatibility. > > > > > On Saturday, 9 August 2014 09:18:11 UTC-5, Spokes wrote: >> >> Thank you for the demo - very useful! It would be fantastic if there were >> a web2py module or feature that implements this sort of functionality. >> >> However, I'm curious as to why it's necessary to use >> "uploadseparate=True" for the upload fields in the db table. Is there a way >> to get this to function with "uploadseparate=False" instead? If not, is >> there a convenient, automatic way, when a file and its thumbnail are >> deleted, to have their folders deleted as well? Thanks! >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
