Hi guys - thanks for the replies.
I guess what I'm trying to do is get the file references inserted into
the DB so that I don't have to do any custom procesing when retrieving
data. Parsing the path once it's retrieved is an option, but creates
complications when viewing stuff in admin etc.
At the moment, when I pass a file using an absolute path like this:
obj.image = "/path/to/media/some-image.jpg"
obj.save
The image gets processed as I'd expect, but the full path gets saved
in the DB, rather than it being truncated to a relative path. I
imagine this is because FileFields don't expect this kind of hacking,
and perhaps I need to take a closer look at the code and think about
whether a patch might be the way to go.
On 27/07/06, John Lenton <[EMAIL PROTECTED]> wrote:
>
> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> >
> > You could just strip the path out and get the filename when you extract
> > the file from the database. Something like:
> >
> > def get_file_without_path(self):
> > start=self.file.rfind('/')
> >
> > return self.file[start+1:]
>
> umm.. os.path.basename() would probably be better than assuming '/'
> (or anything else) is the path delimiter, no?
>
> --
> John Lenton ([EMAIL PROTECTED]) -- Random fortune:
> The trouble with a lot of self-made men is that they worship their creator.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
