Django Model Loop

Question

I am just starting developing with Django, and I'm slowly falling in love. However, i am quite a noob still and have a hard time understanding why this particular model isn't working, so here I am.

I have this model in models.py:

class projectBuildTests(models.Model):
    project = models.CharField(max_length = 50)
    build = models.CharField(max_length = 10)
    testName = models.CharField(max_length = 50)

My view.py goes like this:

def home(request):
    projects = projectBuildTests.objects.all()
    return render_to_response('testrunner/home.html')

in my home.html I am trying to show it like this:

<label>Project:</label><br>
<select class="project_test_selector" multiple="multiple" size="10">
    {% for project in projects %}
    <option>{{ project.text }}</option>
    {% endfor %}
</select>

I am managing the models data with the django admin. It's registered like this:

admin.site.register(projectBuildTests)

In the actual admin-panel the model is showing a bit strange. It gives me a bunch of sub-objects instead of a normal column list which I can append data to. I don't know if I'm making sense here :-/

In your view function, you don't pass the objects variable to the template, so it does nothing. — RemcoGerlich
– RemcoGerlich, Commented Feb 12, 2014 at 10:20
Also as a style guide - don't use camel-case for python class names projectBuildTests should be ProjectBuildTests — Ashley
– Ashley, Commented Feb 12, 2014 at 10:25

Priyank Patel · Accepted Answer · 2014-02-12 10:34:35Z

3

In your views.py, you need to pass projects queryset in context of response.

from django.template import RequestContext
def home(request):
    extra_context = {}
    projects = projectBuildTests.objects.all()
    extra_context['projects'] = projects
    return render_to_response('testrunner/home.html', extra_context, context_instance=RequestContext(request))

And in Your Template:

<label>Project:</label><br>
<select class="project_test_selector" multiple="multiple" size="10">
    {% for project in projects %}
        <option>{{ project.testName }}</option>
    {% endfor %}
</select>

edited Feb 12, 2014 at 10:34

answered Feb 12, 2014 at 10:23

Priyank Patel

3,56523 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

RemcoGerlich Over a year ago

This will throw an error because extra_context isn't defined.

Priyank Patel Over a year ago

:D . forget to initialize dictionary . Edited .

Viktor Over a year ago

I see. Now it gives me a Nameerror: global name 'extra_context' is not defined

Matthias Over a year ago

You could just use render, then you don't have to fiddle with the request context yourself.

Mrav · Accepted Answer · 2014-02-15 09:59:27Z

0

To edit a little Priyank Patel's response.. Django shorcuts are very useful. For example, you can import render:

from django.shortcuts import render

Then just return:

return render(request, 'testrunner/home.html', extra_context)

answered Feb 15, 2014 at 9:59

Mrav

331 silver badge6 bronze badges

2 Comments

Viktor Over a year ago

when would this be more useful than a normal rendertoresponse? Or rather, what's the difference there?

Mrav Over a year ago

It's the same thing. 'render' is just a shortcut for render_to_response.

Collectives™ on Stack Overflow

Django Model Loop

2 Answers 2

4 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related