This is not only an issue with Windows; any filesystem with a filename limit (however big) can hit this problem. As this is all being handled by web2py, and the user is selecting the file to upload, where would this "logic" go, and why isn't web2py handling it?
- Scott On Saturday, March 16, 2013 at 1:04:28 PM UTC-4, Niphlod wrote: > > I was wrong. the first part of the "hash" is a uuid, the second is a > base16 encoding of the original filename. > > Seems that you need some logic to cut down long files if you plan to host > on Windows. > > http://web2py.com/books/default/chapter/29/07?search=uploads#Storing-the-original-filename > > <http://www.google.com/url?q=http%3A%2F%2Fweb2py.com%2Fbooks%2Fdefault%2Fchapter%2F29%2F07%3Fsearch%3Duploads%23Storing-the-original-filename&sa=D&sntz=1&usg=AFQjCNHoAJ_7v4pFTQfLJ7w7itNYEBhoPw> > -- 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.
