Thanks for the reply Russ. I will check into different things, you make it sound easier than it looks. :)
On Feb 4, 11:33 pm, Russell Keith-Magee <[email protected]> wrote: > On Thu, Feb 5, 2009 at 1:09 PM, issya <[email protected]> wrote: > > > Thanks for the reply. I was aware of that but I guess I don't > > understand how to go about using it. I do understand that I can > > serialize a queryset. But I cannot just go and use the serialized data > > as template context. From the options I've seen, it looks like if I > > did something like that I would have to process everything with the > > javascript including iterating through the data and making an html > > layout. I may be confused though, little sleep and a lack of knowledge > > will do that. > > There is no need for templates to be involved at all. Django's > serializers will turn a queryset into a serialized string. That string > can be provided literally as the content for a HttpResponse (just > remember to set the content type for the response to suit the > serialization format). You don't need to go through a template > rendering process on top of this. > > What you then do on the client side is entirely up to you - jQuery > provides some nice deserialization methods for AJAX requests, but > there are many other options. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
