On Tue, May 12, 2009 at 4:24 AM, Alex Rades <alera...@gmail.com> wrote:
> > Hi, > I'd like to save my images using this schema (which is, I think, > something 99% of web sites do): > > def upload_to(instance, filename): > return "photos/%s/%s"%(instance.pk % 1000, filename) > > the problem is that, as mentioned in the documentation about the > "instance" parameter of upload_to: > > "In most cases, this object will not have been saved to the database > yet, so if it uses the default AutoField, it might not yet have a > value for its primary key field." > > So I have two questions: > > - Is there a workaround to obtain my desired behaviour? > - Why the model isn't saved to the db before calling upload_to? > > > > 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. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
