On Tue, Jul 13, 2010 at 1:37 AM, Ric wrote:
> hi russ i have been on a wedding!
>
> ok, now i see the point.
>
> but what i was tring to say is that adding a simple version of this
> feature would be a plus to the actual version of django, with hooks it
> would be a great plus.
>
> i think that de
hi russ i have been on a wedding!
ok, now i see the point.
but what i was tring to say is that adding a simple version of this
feature would be a plus to the actual version of django, with hooks it
would be a great plus.
i think that definition of public API is something that should be done
afte
On Fri, Jul 9, 2010 at 10:37 PM, Ric wrote:
> i'll reply one by one
>
> * What if you have multiple models referring to Author? Do you
> assume
> that every related model will be updated the same way?
>
> * What if you have multiple foreign keys from Blog to Author? Do you
> assume that every fo
i'll reply one by one
* What if you have multiple models referring to Author? Do you
assume
that every related model will be updated the same way?
* What if you have multiple foreign keys from Blog to Author? Do you
assume that every foreign key on a single model will be updated in
the
same way
On Thu, Jul 8, 2010 at 11:19 PM, Ric wrote:
> Hi Russ, nice to talk with u,
>
> i think that we can focus only on substitute feature,
> to archive it we have 2 options:
>
> simply upgrade the current delete_view or make a new view, something
> like
> url(r'^(.+)/substitute/$',
>
i took this idea from wordpress. in wordpress when you delete an user
instead of deleting all related posts you can choose to assign them to
another user.
we can extend this system on every model class, i think.
whatch here, sorry wordpress is in italian (hope u understand a
little)
http://grab.b
Hi Russ, nice to talk with u,
i think that we can focus only on substitute feature,
to archive it we have 2 options:
simply upgrade the current delete_view or make a new view, something
like
url(r'^(.+)/substitute/$',
wrap(self.substitute_view),
name='%
Just last week I need to implement something like option 2 in a generic crud
(people that command project doesn't liked admin ...), so what I simple
customized delete of model and force app to call delete of model when
deleting more than one object.
So, I really vote +1 for this kind of change.
2
On Wed, Jul 7, 2010 at 3:41 PM, Ric wrote:
> Hello i opened a ticket, but somone suggest me to discuss this new
> feature here.
>
> http://code.djangoproject.com/ticket/13900
>
> i would like to edit
> django.contrib.admin.options.ModelAdmin?.delete_view and add a helpful
> feature.
>
> Inste
Hello i opened a ticket, but somone suggest me to discuss this new
feature here.
http://code.djangoproject.com/ticket/13900
i would like to edit
django.contrib.admin.options.ModelAdmin?.delete_view and add a helpful
feature.
Instead of deleting all the nested objects, the delete_view could
h
10 matches
Mail list logo
