Re: IMPORTANT: Django model syntax is changing

2005-08-26 Thread Jason F. McBrayer
On Fri, 2005-08-26 at 13:33 -0500, Adrian Holovaty wrote: > On 8/26/05, Jason F. McBrayer <[EMAIL PROTECTED]> wrote: > > > In [1]: from django.models.engulf import feeds, users, articles, categorys > > > In [2]: c = categorys.get_list(user_id__exact=1) > > You want categorys.get_list(user__id__ex

Re: IMPORTANT: Django model syntax is changing

2005-08-26 Thread Adrian Holovaty
On 8/26/05, Jason F. McBrayer <[EMAIL PROTECTED]> wrote: > > In [1]: from django.models.engulf import feeds, users, articles, categorys > > In [2]: c = categorys.get_list(user_id__exact=1) You want categorys.get_list(user__id__exact=1) -- a subtle change. With the new syntax, calling code never r

Re: IMPORTANT: Django model syntax is changing

2005-08-26 Thread Jason F. McBrayer
The new syntax breaks get_list() for me. Here's an excerpt from my model: class Category(meta.Model): name = meta.CharField("Name of Category", maxlength=255) user = meta.ForeignKey(User) feed = meta.ManyToManyField(Feed, filter_interface=meta.VERTICAL) class META: admin

IMPORTANT: Django model syntax is changing

2005-08-25 Thread Adrian Holovaty
All, By popular demand, I'm about to change Django's model syntax to use "fieldname = FieldClass" instead of "FieldClass('fieldname')". This has been a longstanding ticket -- http://code.djangoproject.com/ticket/122. This change is BACKWARDS-INCOMPATIBLE, so don't "svn update" your code until yo