Re: Any known issues with ChangeManipulators and large objects?
On Mon, 2007-03-12 at 10:27 -0700, Joseph Heck wrote: > Kudo's to Ivan - It's a pretty good answer. I think the metaphor > breaks down when you get to >1000 items that could pop up in a select > field, but at least you don't get his when just using a plain-jane > manipulator with this fix. > > I think I'll stick with the tendency towards using raw_id_admin=True > myself, but then I don't need anything populated into a large > pulldown. My case would have a pulldown of 30K+ items, which just > doesn't make sense for a UI. I think that's the important thing here: we are currently paying a performance penalty for retrieving all the related foreign key elements, even in cases when it was impractical to display them. 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: Any known issues with ChangeManipulators and large objects?
Kudo's to Ivan - It's a pretty good answer. I think the metaphor breaks down when you get to >1000 items that could pop up in a select field, but at least you don't get his when just using a plain-jane manipulator with this fix. I think I'll stick with the tendency towards using raw_id_admin=True myself, but then I don't need anything populated into a large pulldown. My case would have a pulldown of 30K+ items, which just doesn't make sense for a UI. -joe On 3/12/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Mon, 2007-03-12 at 17:37 +1100, Malcolm Tredinnick wrote: > > On Mon, 2007-03-12 at 05:00 +, [EMAIL PROTECTED] wrote: > > > I was just wondering if there were any known issues regarding speed > > > with ChangeManipulators and large objects? > > > > > > I'm using custom ChangeManipulators successfully on about 50 pages > > > right now... but when I did an edit page for one of my largest > > > database tables ( about 50 columns... and about 20 of them are foreign > > > keys to other objects that also contain foreign keys ), my page load > > > time shot up to about 30 seconds. > > > > > > If I comment out the line where I instantiate the custom change > > > manipulator..and just pass None in for the Form ... it loaded fast > > > (obviously blank forms load fast..heh). So then I decided to rewrite > > > the page using old fashioned forms where I set the values on each > > > field in the template via the object...and it went really fast then > > > too. > > > > > > I could paste the code in here..but I wasn't doing anything fancy.. I > > > was just flattening the data from all of the objects...then loading > > > the form...so thought I'd ask on the off chance if others had seen > > > this happen? > > > > Unfortunately there is a problem in that case (foreign keys with lots of > > related data). It is ticket #2638. > > It also looks like the patch in #3436 might be a solution for this. That > has the sort of solution I was hoping for in #2638. > > 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: Any known issues with ChangeManipulators and large objects?
On Mon, 2007-03-12 at 17:37 +1100, Malcolm Tredinnick wrote: > On Mon, 2007-03-12 at 05:00 +, [EMAIL PROTECTED] wrote: > > I was just wondering if there were any known issues regarding speed > > with ChangeManipulators and large objects? > > > > I'm using custom ChangeManipulators successfully on about 50 pages > > right now... but when I did an edit page for one of my largest > > database tables ( about 50 columns... and about 20 of them are foreign > > keys to other objects that also contain foreign keys ), my page load > > time shot up to about 30 seconds. > > > > If I comment out the line where I instantiate the custom change > > manipulator..and just pass None in for the Form ... it loaded fast > > (obviously blank forms load fast..heh). So then I decided to rewrite > > the page using old fashioned forms where I set the values on each > > field in the template via the object...and it went really fast then > > too. > > > > I could paste the code in here..but I wasn't doing anything fancy.. I > > was just flattening the data from all of the objects...then loading > > the form...so thought I'd ask on the off chance if others had seen > > this happen? > > Unfortunately there is a problem in that case (foreign keys with lots of > related data). It is ticket #2638. It also looks like the patch in #3436 might be a solution for this. That has the sort of solution I was hoping for in #2638. 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: Any known issues with ChangeManipulators and large objects?
On Mon, 2007-03-12 at 05:00 +, [EMAIL PROTECTED] wrote: > I was just wondering if there were any known issues regarding speed > with ChangeManipulators and large objects? > > I'm using custom ChangeManipulators successfully on about 50 pages > right now... but when I did an edit page for one of my largest > database tables ( about 50 columns... and about 20 of them are foreign > keys to other objects that also contain foreign keys ), my page load > time shot up to about 30 seconds. > > If I comment out the line where I instantiate the custom change > manipulator..and just pass None in for the Form ... it loaded fast > (obviously blank forms load fast..heh). So then I decided to rewrite > the page using old fashioned forms where I set the values on each > field in the template via the object...and it went really fast then > too. > > I could paste the code in here..but I wasn't doing anything fancy.. I > was just flattening the data from all of the objects...then loading > the form...so thought I'd ask on the off chance if others had seen > this happen? Unfortunately there is a problem in that case (foreign keys with lots of related data). It is ticket #2638. 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 -~--~~~~--~~--~--~---
Any known issues with ChangeManipulators and large objects?
I was just wondering if there were any known issues regarding speed with ChangeManipulators and large objects? I'm using custom ChangeManipulators successfully on about 50 pages right now... but when I did an edit page for one of my largest database tables ( about 50 columns... and about 20 of them are foreign keys to other objects that also contain foreign keys ), my page load time shot up to about 30 seconds. If I comment out the line where I instantiate the custom change manipulator..and just pass None in for the Form ... it loaded fast (obviously blank forms load fast..heh). So then I decided to rewrite the page using old fashioned forms where I set the values on each field in the template via the object...and it went really fast then too. I could paste the code in here..but I wasn't doing anything fancy.. I was just flattening the data from all of the objects...then loading the form...so thought I'd ask on the off chance if others had seen this happen? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
