1. If i have the USA phone directory as my DB, and NY has 10,000,000 records in it. or i have a DB with only NY 10,000,000 records without the rest of the USA. searching for all NY records will take same time at both cases ?
2. The other reason to split the DB is security, should a "bug" or a google app exploit will be available you dont want your customer "A" records be viewed by customer "B". the application runs in somekind of sandbox but if the DB is one any small error in program can expose everything to everyone. Eddie. On Wed, Jun 17, 2009 at 4:22 PM, Wooble <geoffsp...@gmail.com> wrote: > > > > On Jun 17, 2:35 pm, "Eddie Harari" <eddie.har...@gmail.com> wrote: > > But it seems to me that the more data you have on that single application > > the more queries will be inefficient. > > > > Cause if I have stored 40000 objects in my DB and one user has only 500 > > objects in the DB , I will need to go over all the 40,000 objects to find > > > > His data ? is that correct ? > > No. The database queries on indexes, it doesn't scan the entire table. > The time it takes to fetch entities returned by a query is entirely > dependent on the number of entities you fetch, not on the size of your > database. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
