I'm one of those who participated in ticket #2145 discussion. I must
admit you have the most sane and comprehensive opinion I ever heard on
the 1-to-1 problem. Completely agreed on the every point.. And no, I
don't see any other way on practically extending the models for
natural and DRYish reusin
I've run into this problem when using dbsettings / django-values in my
project, but the source of the problem actually lies deeper.
There's a core class django.db.models.loading.AppCache which populates
the list of project apps and models. It works pretty well unless a
specific set of conditions
> It also occurs to me that if regroup handled QuerySets as a special case,
> large-ish datasets could be regrouped in a much more efficient manner, since
> the
> filter method could be used instead of iterating and testing for equality.
First, there will be no perfomance gain at all.
Consider
+1 on that. Have been in the same situtation and came up with the
exactly same approach on my mind.
Perhaps http://code.djangoproject.com/ticket/1513 should be reopened?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
Marty,
Thanks for your work!
I run into the problem that the module doesn't seem to work well with
Apache+mod_python. The new values are actually saved to the db, but
not used until I restart Apache (neither as class members nor in the
admin settings panel). I think that's because of the per-pro
I've been thinking on the equality issues a couple of days before.
What I was trying to achieve was to construct a set() of (presumably,
different) model objects.
The intuitive approach:
>>> a = User.objects.get(id=1)
>>> b = User.objects.get(id=1)
>>> set([a,b])
set([, ])
...didn't work (the s
ject.com", but I
don't like the package to be named "project.com" (I'm not even sure
that it's possible to have dots in the package name).
I've found several threads in this group regarding this issue, but no
decent solution or even comments. How do most of people
