Totally agree, bulk delete shouldn't be enabled by default.
One more issue with that: it is nice to be able to define actions
order in drop-down list. It can be achieved with very simple patch,
see http://code.djangoproject.com/ticket/10734 . But if we have delete
action (or any other action) ena
On Sat, Apr 4, 2009 at 7:10 PM, kmike wrote:
>
> Totally agree, bulk delete shouldn't be enabled by default.
>
> One more issue with that: it is nice to be able to define actions
> order in drop-down list. It can be achieved with very simple patch,
> see http://code.djangoproject.com/ticket/10734
On Apr 3, 9:50 am, Jeremy Dunck wrote:
> Gary, Justin?
>
The 17th option is better for me, but at this point it's still not
looking like I'll be able to make it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
2009/3/22 Daniel Tang
>
> On Sun, Mar 22, 2009 at 11:55, Christian Schilling
> wrote:
>
> > 2) a API like the current django-denorm to turn functions into fields.
> > this could work by creating a model DirtyInstance that contains
> > nothing but a generic FK
> > when such a field is used it sho
Hi Jacob,
Just got back from being away, would have replied earlier otherwise...
> It's simply far too draconian: if I forget to do all steps needed
> to upgrade, all my contrib apps stop working. And then as soon as I
> *do* those steps, all *my* apps that use POST stop working. I just
> can't
