Johnny Blonde <[EMAIL PROTECTED]> writes: > the IN-query-tip by jorge is really speeding up things.
Good to know that something has improved. > but actually i´m not even sure if it´s the queries slowing down > everything: sometimes i display just a long list (table) with let´s > say 1200 entries with customer names and additional info, this takes > around 12 seconds from request to display. And do someone *really* need to look at 1200 entries at the same time? > then i have another page, with the same clients, but with checkboxes > for each client (around 16 per client --> 16*1200 = 19.200 > checkboxes). and this page takes around 1-1.5 minutes to be displayed. > > even though there are some more queries in this page, too, i think it > ´s just the browser needing more time to render all the form-fields > instead of plain text-nodes. It might be. But people won't bother with more than a few tens of options, and nobody would change one option for 1200 entries all at once... Your controller will also get mad :-) It's too much. Think about why websites like Google and Multiply restrict your view to at most 100 items. Think about paginating your data. It might be better for the user to change one or 10 entries at the same time instead of 1200... Think that space on your screen is worth a lot of gold and value that space. Don't make your users loose their attention or pull out their hair with so many changes (or with a problem when submitting the form and loosing 4321 changes made on several differente entries). Too much == Too bad most of the times. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
