[va1en0k]

And, of course, you can use multiple different dj.FileFields for that in one model, if you need only a limited number of images.

[bmelton]

Oh, I don't mind using a separate table or anything, I'm just not entirely sure if, because you're storing the files, whether or not that changes the default paradigm.

I might have worded my initial question poorly: but I could very easily have seen if the FileFields field stored a link to a bucketized URL or something, or even an array of URIs. If it's one-to-one, then that's fine, and actually means less changes to my code; I'm just not sure.

Obviously, a quick prototype will show me exactly how to implement, but I thought I'd ask while the question was hot.

[va1en0k]

For now, it can be only a separate table. In the future, of course, there're going to be buckets and everything, stay tuned!

If you have some specific ideas about this in mind, my email is [e-mail]