That makes sense.
While my proposal isn't made for a sake of proposing something, I see
that I hardly can speed up implementing it without following your last
advice and working on other Django ORM issues. I'm going to find out
what I can do.
Thanks.
--
Best Regards,
Valentin Golev
Lead Develope
On Wed, Jul 21, 2010 at 6:02 PM, Valentin Golev wrote:
> Thanks for your reply.
>
> 'You have SQL, go write some, our ORM already contains everything what
> Django needs' - that's what you say, am I getting it right? I'm
> confused by your answer. But I can't argue with that, if it's Django
> stra
Thanks for your reply.
'You have SQL, go write some, our ORM already contains everything what
Django needs' - that's what you say, am I getting it right? I'm
confused by your answer. But I can't argue with that, if it's Django
strategy, well, I have to respect it.
You said that's extending ORM is
I like screwing these counters to model
try something like that.
class RegistrationProfile(models.Model):
"""
A simple profile which stores an activation key for use during
user account registration.
Generally, you will not want to interact directly with instances
of this mode
On Wed, Jul 21, 2010 at 1:17 AM, Valentin Golev wrote:
> Hello,
>
> There is a common situation for almost all of my projects. Maybe it's
> my mistake somewhere, maybe Django really lacks of some ability.
>
> Let's suppose a simple structure:
>
> model User;
> model Message ( from=User, unread=boo
Hello,
There is a common situation for almost all of my projects. Maybe it's
my mistake somewhere, maybe Django really lacks of some ability.
Let's suppose a simple structure:
model User;
model Message ( from=User, unread=bool )
I want to get a list of all Users with counts of all messages from
