> that returns the variation that corresponds to currently chosen
> > language, and use this function in all the views instead of the actual
> > fields. Are there any other patterns in place? Just don't want to
> > invent a wheel here.
> >
>
--
Vale,
Dmitry Rubin
models class that
> > is called, say, filter_by_user, and whose value is the name of the
> > field which is a foreign key into the User table, and a corresponding
> > code in the admin views that filters by this field). Is this patch
> > likely to be excepted into the django
2 matches
Mail list logo