On Wed, Jan 19, 2011 at 4:04 AM, Sithembewena Lloyd Dube <zebr...@gmail.com> wrote: > Hi all, > > I am building a search app. that will query an API. The app. will also store > search terms in a very simple table structure. > > Big question: if the app. eventually hit 10 million searches and I was > storing every single search term, would the table hold or would I run into > issues? > > Also, is it "ok" to check if each search query exists or not while I save > it, so I can update it's count (times searched), or should I rather forget > that and do the counts in a custom reporting function/ sql query? > > I am kind of worried that the Django database API is may not deal with all > these too gracefully. NB - I am not cool with tinkering with models > (especially not object relationships) too much when I have to maintain this > in a year or two. > > I guess I am learning about proper database schema design.
Django won't be a the constraining factor here. Django's ORM is a relatively light wrapper around SQL. So the real question is "can you create a 10 million row database with SQL"? The answer is "of course you can... but". If you've done everything right -- good schema design, index use appropriate to your queries, and so on -- then 10 million rows won't pose a major problem. However, it's also fairly easy to set up a 10 million row table that you *can't* search efficiently. Using Django doesn't change anything in this equation -- it just composes the query and wraps the result. Yours, Russ Magee %-) -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
