On Fri, May 9, 2008 at 12:46 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
> As a hint to the community - one of the best suggestions we can have
> at this stage of the project is a set of interesting problems to
> solve. This would give us a set of concrete 'problems' that we can use
> to
All of this looks pretty good. The 2 things I have to say are, a) I
think the F() way of dealing with that, in place of list comprehension
is the right way to go, there has been a lot of good work on that
patch, and I think it works well, conceptually, with this. b) Is there
any plan to make
Simon Willison wrote:
> How about mysql_masterslave or mysql_replicated (I prefer the second)?
Yes, mysql_replicated seems right. Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
Hi Russell,
I have been adding your test cases to the test suit and ran into
troubles with some of them so I would like to know a bit more on what
you were expecting from the queries:
> * Does Author X have any friends?
> (aggregate on a related object)
>
