On Wed, Oct 5, 2011 at 12:38 PM, Martin Pool <email address hidden> wrote:
> On 5 October 2011 10:27, Robert Collins <email address hidden> wrote:
>> I suggest returning the master - thats more consistent with our user
>> model around bugs, notifications etc.
>
> I think that would be best, but since the db is timing out at the
> moment even returning the current list, I hesitate to specify
> something that will require doing even more work (a self join to find
> the master.)
You can do that as a separate query, or work on that after the timeout
is addressed.
On Wed, Oct 5, 2011 at 12:38 PM, Martin Pool <email address hidden> wrote:
> On 5 October 2011 10:27, Robert Collins <email address hidden> wrote:
>> I suggest returning the master - thats more consistent with our user
>> model around bugs, notifications etc.
>
> I think that would be best, but since the db is timing out at the
> moment even returning the current list, I hesitate to specify
> something that will require doing even more work (a self join to find
> the master.)
You can do that as a separate query, or work on that after the timeout
is addressed.