On Tue, Feb 21, 2012 at 10:55 PM, Thomas Woolford <[email protected]>wrote:
> Any files uploaded when the clone view is submitted will be uploaded on > save and associated with the new object anyway. > It is perfectly valid for two DB rows to point at the same file because as > soon as that file is re-uploaded it creates a new file instead of > overwriting the old one anyway > But this behaviour doesn't represent all cases. In some cases, the users could be want to "clone" in a full copy and a representation of files too and NOT link to the pre-existing files of the other/s objects. This mean that if I change the "origin" object file, the cloned/s objects will change their links too? The obviously behaviour will be to copy another file on the server and associate it with this new object and be consistent with the default admin functionality. Regards, -- juanpex -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
