Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-24 Thread Dan Gentry
Agree with Tom that ccbv is a great resource for help with CBVs. In fact, I used it to help me with this comment. I would probably override the delete() method in DeleteView to do what you want to do. The original justs deletes the record and redirects to the supplied URL: 1. def delete(

Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-21 Thread Tom Christie
> Is there a site, where I can found such things like What happens in a CBV View? http://ccbv.co.uk is really great resource. Can't recommend it highly enough. On Thursday, 21 March 2013 13:23:05 UTC, Christian Schmitt wrote: > > Hi, yeah that definitly helps. > I didn't found a good site whe

Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-21 Thread Christian Schmitt
Oh, yeah you gave me a good idea, but no, DELETE is fine. Since I wanted to do an ajax request anyway. Am Donnerstag, 21. März 2013 14:22:59 UTC+1 schrieb Tom Christie: > > Actually you'll probably want the `delete` method to be a `post` instead, > but either way hopefully it'll give you the righ

Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-21 Thread Christian Schmitt
Hi, yeah that definitly helps. I didn't found a good site where CBVs getting described in that way. Is there a site, where I can found such things like What happens in a CBV View? It's way easier to understand the whole CBV thing. Btw. FBVs are way easier than CBVs but with FBVs I need to copy &

Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-21 Thread Tom Christie
Actually you'll probably want the `delete` method to be a `post` instead, but either way hopefully it'll give you the right idea. On Thursday, 21 March 2013 13:11:44 UTC, Tom Christie wrote: > > In cases like this, rather than rely on overriding the default behavior of > the DeleteView, > I'd rec

Re: Django 1.5 CBV - DeleteView - CustomQuery

2013-03-21 Thread Tom Christie
In cases like this, rather than rely on overriding the default behavior of the DeleteView, I'd recommend writing your own base class. It'll be more explicit and more obvious exactly what is going on... from django.views.generic import View class MarkDeletedView(View): """