Zak Johnson wrote:
> class Item(models.Model):
> is_active = models.BooleanField()
> objects = ActiveManager()
> inactive_objects = InactiveManager()
In case anyone else runs into this problem, the workaround I'm using for
now is simply to add a new default manager which contains all
On Fri, 2008-12-12 at 19:22 -0800, Zak Johnson wrote:
[...]
> Am I missing something, or is this simply unsupported now? The
> documentation notes that it's "a good idea to be careful in your choice
> of default manager," but doesn't clearly state that a model's default
> manager must not filter
I'm porting one of my applications to 1.0, and have come across what
seems like a bug related to the Queryset refactor. Previously, it was
possible to have a model's default manager filter the results; something
like:
class ActiveManager(models.Manager):
def get_query_set(self):
qs =
On Fri, 2008-12-12 at 09:31 -0800, alex.gay...@gmail.com wrote:
> Malcolm,
>
> I've updated the ticket with a newer patch that removes the messy
> globals system, now the form's full_clean() method passes a callable
> to each clean method that accepts it, this callable simply uses
> closure to k
Malcolm,
I've updated the ticket with a newer patch that removes the messy
globals system, now the form's full_clean() method passes a callable
to each clean method that accepts it, this callable simply uses
closure to keep the current field name and it calls the add_warning
method on the form it
Thanks for the reply. I have created a ticket (http://
code.djangoproject.com/ticket/9819). And added a small patch.
More patches to come.
On Dec 8, 10:10 pm, "Jacob Kaplan-Moss" wrote:
> On Mon, Dec 8, 2008 at 4:20 AM, Kegan wrote:
> > Is there an active effort in working on the docs?
>
> The
