Re: Bug? Related manager not working for custom manager?
Ian, Thanks for the reply, yes I've verified via the db.connections option that something is definitely wrong. John On Nov 19, 6:33 pm, "Ian Lewis" <[EMAIL PROTECTED]> wrote: > John, > > Try checking the log output of the database server to see what is > different about the SQL. Perhaps some kind of caching is going on > where the manager is caching the results of it's queries? > > On Thu, Nov 20, 2008 at 11:21 AM, John M <[EMAIL PROTECTED]> wrote: > > > I have a model with a custom model manager used for related set > > filtering, but it's not working as expected. > > > See my models and test athttp://dpaste.com/92327/ > > > Can someone explain why my manager isn't doing what I think it should? > > > Thanks > > > John > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Bug? Related manager not working for custom manager?
Malcom, Thank you so much for taking the time to look over this, and you're right, looking back, I should have trimmed down the problem for all to see. I've come up with a work-around for now, but will watch the ticket to see when it's fixed. I suspect it's something to do with the fact it's a related manager, cause working with the records as Tasks directly, doesn't seem to have the problem. Thanks again John On Nov 19, 11:52 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2008-11-19 at 18:21 -0800, John M wrote: > > I have a model with a custom model manager used for related set > > filtering, but it's not working as expected. > > > See my models and test athttp://dpaste.com/92327/ > > > Can someone explain why my manager isn't doing what I think it should? > > This would have been a good situation to really trim down your example > to, say, one extra field plus the ForeignKey in each model. It took a > fair amount of work to untangle your test lines that didn't have any > explanation of what you expected to see and work out what the problem > was that you were actually seeing. Remember that you're always going to > be more familiar with the problem than the people reading it anew. > > After trimming down the example, we end up with ticket #9643. It's a > clearbug. My guess is that it will be easy to fix when I get a few > minutes to look at it. > > Regards, > Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Bug? Related manager not working for custom manager?
On Wed, 2008-11-19 at 18:21 -0800, John M wrote: > I have a model with a custom model manager used for related set > filtering, but it's not working as expected. > > See my models and test at http://dpaste.com/92327/ > > Can someone explain why my manager isn't doing what I think it should? This would have been a good situation to really trim down your example to, say, one extra field plus the ForeignKey in each model. It took a fair amount of work to untangle your test lines that didn't have any explanation of what you expected to see and work out what the problem was that you were actually seeing. Remember that you're always going to be more familiar with the problem than the people reading it anew. After trimming down the example, we end up with ticket #9643. It's a clear bug. My guess is that it will be easy to fix when I get a few minutes to look at it. Regards, Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Bug? Related manager not working for custom manager?
John, Try checking the log output of the database server to see what is different about the SQL. Perhaps some kind of caching is going on where the manager is caching the results of it's queries? On Thu, Nov 20, 2008 at 11:21 AM, John M <[EMAIL PROTECTED]> wrote: > > I have a model with a custom model manager used for related set > filtering, but it's not working as expected. > > See my models and test at http://dpaste.com/92327/ > > Can someone explain why my manager isn't doing what I think it should? > > Thanks > > John > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Bug? Related manager not working for custom manager?
I have a model with a custom model manager used for related set filtering, but it's not working as expected. See my models and test at http://dpaste.com/92327/ Can someone explain why my manager isn't doing what I think it should? Thanks John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
