Here Jon et al, http://dpaste.com/116323/
Keep in mind this is very draft-y... I'm pretty much just doing this to test and play around with getting the data. Hope this helps and thank you. -Alex On Feb 4, 1:54 am, Jon Loyens <[email protected]> wrote: > Oops... I meant dpaste.com > > On Feb 3, 8:54 am, Jon Loyens <[email protected]> wrote: > > > Alex, would you mind posting your complete template at dpaste.org for > > us to look at? It might clarify how you're trying to do the output. > > > Thanks, > > > Jon. > > > On Feb 2, 11:37 pm, Alexiski <[email protected]> wrote: > > > > > On Mon, 2009-02-02 at 21:21 -0800, Alexiski wrote: > > > > > Hi Malcolm, > > > > > > Thanks for your response, but I'm not quite sure how to iterate using > > > > > obj.query.all to get all the instances I'm after. > > > > > > Could you please provide a code snippet or direct me to a relevant > > > > > page? > > > > > Iteration in templates is done with the forloop template tag. You must > > > > already be using that to iteratate over all the copy instances. > > > > Correct I am using the {% for Copy in object_list %} tag. I access the > > > fields like so - {{ Copy.id }} {{ Copy.question }} > > > > In order to access the n Query objects per Copy object, do I nest {% > > > for Query in object_list %} and access using {{ Query.id }} > > > {{ Query.requirements }} ? > > > > Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
