Am 11.06.2012 22:20, schrieb Anthony:
>
>
> Beat me, but I am using the simplest download function
>
> def download():
> return response.download(request,db)
>
> and it works without database entries.
> Well - I got a table defined like this:
>
> db.define_table("t_files
Beat me, but I am using the simplest download function
>
> def download():
> return response.download(request,db)
>
> and it works without database entries.
> Well - I got a table defined like this:
>
> db.define_table("t_files",
> #Field('file', 'upload', uploadfield='pictur
Am 11.06.2012 21:26, schrieb Anthony:
>
> hm, so the uuid seems to be there to take into account, that
> multiple files with the same filename might be uploaded. That
> makes sense, exspecially if not all files README.txt have the same
> content.
>
>
> If the filename is very long
>
> hm, so the uuid seems to be there to take into account, that multiple
> files with the same filename might be uploaded. That makes sense,
> exspecially if not all files README.txt have the same content.
>
If the filename is very long, part of it might get cut off depending on the
"length"
Am 11.06.2012 19:19, schrieb Anthony:
>
> my application is generating pdfs which should be available via the
> normal web2py download controller.
> I realize, that the file in the uploads/-directory is named like:
>
>
> pdf
>
> But what is the something?
>
>
> Look
>
> my application is generating pdfs which should be available via the
> normal web2py download controller.
> I realize, that the file in the uploads/-directory is named like:
>
> pdf
>
> But what is the something?
>
Looks like it's the last 16 (non-hyphen) characters of a uuid:
htt
6 matches
Mail list logo
