On Tue, May 12, 2009 at 1:02 PM, Alex Gaynor <alex.gay...@gmail.com> wrote:
> The reason the model isn't saved at thie point is because Django stores the > path to the file in the DB. This means it has to know the path to the file > in order to save it. However, you want it to save it in order to construct > the path to the file. I'd solve this by using a post_save handler to move > the file and resave the object with the new location. > Yeah, went that way. Not very clean imho, but I don't see cleaner ways. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
