On 8/23/06, keukaman <[EMAIL PROTECTED]> wrote:
>
> Thank you. I took your advice and changed "photoid" to "entry". I'm new
> to this, so can you elaborate a bit on why it's better to name that
> field 'entry'?
I will assume I'm actually in the same channel that Chris here.
On django models,
{% for photo in object.photo_set.all %}
{% endfor %}
PS: It would be better to call the field 'entry' rather than 'photoid'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
p.s. I'm using generic views
keukaman wrote:
> I wrote a blog application that included a single image. I originally
> wrote my model so that the image was defined in the same class as the
> rest of the blog entries.
>
> I then decided that I wanted to be able to put multiple images into my
>
I wrote a blog application that included a single image. I originally
wrote my model so that the image was defined in the same class as the
rest of the blog entries.
I then decided that I wanted to be able to put multiple images into my
blog, so I created a "Photo" class, with a var called
4 matches
Mail list logo
