mind that there's even another "angle": given that usually a city resides in the same place (same goes for regions, countries, etc etc etc) you can carefully cache the "computationally expensive" resultset and update it once a week (or once modifications are made). That's what we - dba - call as "materialization" process: something huge to compute, read often, modified rarely...can be computed rarely and stored somewhere with the most correct structure that is "read-safe".
On Thursday, February 12, 2015 at 1:27:29 PM UTC+1, Louis Amon wrote: > > a webpage holding 200 locations and requiring 800 queries is not a webpage > a user would need. > > > That’s actually a very good point ! > > This page is actually designed for SEO, but even SEO doesn’t go well with > hundreds of links. > > I think I should build a navigation architecture that maps the drill down > I want to build. > This way I solve both problems : the DAL query will be much simpler & the > result in terms of SEO will also improve ! > > Thanks Niphlod for helping me clear that up. Not all answers need to be > technical :) > > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
