It's a bad design choice using a single table with lots of fields plus an attachment (if the attachment is large). I always store attachments in a separate table.
That being said, I don't think that keepvalues will do the trick, cause basically keepvalues sends back to the client the contents and prefills the field ... throwing the file back to the client doesn't **sound smart**. However, it's a chicken-and-egg problem.... let's say you want to upload a picture, you require the picture to have a tag, but the user forgets it..... in this case, retaining in some way the file can be done... But let's say you want the file to end with .txt only ..... the .exe file should be discarded at all. It's up to you to provide logic consistent with the workflow you want for your users ..... /me would provide an async upload, store the id on the session and let the user play with the remaining fields in a form. Everyday I'd prune all the attachments received with no "remaining fields" attached. On Thursday, March 28, 2013 5:08:24 PM UTC+1, Lamps902 wrote: > > When a form has errors, the value of an upload field is reset upon > submission. Is there a way to retain this value, or does this pretty much > have to be handled manually (i.e. by storing the value of the upload field > or by prompting the user to specify the file again)? > -- --- 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/groups/opt_out.
