On Dec 17, 2007 5:36 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Yes, right. But here is patch from 8 months ago:
> http://code.djangoproject.com/attachment/ticket/3275/fix_depth_bug.diff
> and why it isn't in branch head?
Perhaps you didn't read the information on that ticket, which
On Mon, 2007-12-17 at 03:36 -0800, [EMAIL PROTECTED] wrote:
> Yes, right. But here is patch from 8 months ago:
> http://code.djangoproject.com/attachment/ticket/3275/fix_depth_bug.diff
> and why it isn't in branch head?
All those bugs are being fixed on the queryset-refactor branch. I hadn't
Yes, right. But here is patch from 8 months ago:
http://code.djangoproject.com/attachment/ticket/3275/fix_depth_bug.diff
and why it isn't in branch head?
On 17 Gru, 12:28, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-12-17 at 03:25 -0800, [EMAIL PROTECTED] wrote:
> > I found bug
On Mon, 2007-12-17 at 03:25 -0800, [EMAIL PROTECTED] wrote:
> I found bug in Django ORM. In function select_realted is a parameter
> 'depth' which works wrong. If I set depth=1, Django getting related
> tables with depth=2.
Always worth having a quick search in Trac for things like this. This
I found bug in Django ORM. In function select_realted is a parameter
'depth' which works wrong. If I set depth=1, Django getting related
tables with depth=2.
The bug is in file db/models/query.py in function fill_table_cache,
where is:
if max_depth and cur_depth > max_depth:
return
