On Aug 11, 1:39 pm, Ole Laursen <o...@iola.dk> wrote: > 1) a convenient file pointer for facilitating the upload machinery > 2) a field for storing a file, just like storing it directly in the > database except we put the data in the file system
No conclusion? Here are some options 1. Apply the patch in 11663 more or less as is. Pros: no API breakage. Cons: all FileField objects are leaking unless you do something. Deleting an object with a FileField causes full table scan (unless you add an index yourself). 2. Apply the patch, but turn on orphan deletion by default. Pros: FileField is leak-free out of the box. Cons: API break if you were relying on the garbage, deleting still causes full table scan. 3. FileField owns the file it points to. Pros: no leak, simple code, no table scans. Cons: API break if you were relying on two objects pointing to the same file. 4. As 3, but add option to be more in line with current behaviour. So API break, but it's easy to fix. Ole --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
