[google-appengine] Re: datastore advice?

Hi Ikan Lan, I have seen this on so many discussions here in the forums - "A best practice, however, is to keep entity groups as small as possible" As far as I understand it, one Model class should not have too many records i.e. one table should not have many records Isn't this strange ? When we

[google-appengine] Re: datastore advice?

my apologies for the word typo, i meant the same but my question still remains - if we have to store 1 million customer records, do we create 100 different "Kinds" ~= Entity Groups ~= db.Model and distribute those 1 million records among those entity groups ? then what about scalability ? does th

[google-appengine] Re: datastore advice?

Thanks everyone, I got the point :) Cheers ! On Oct 30, 10:34 pm, Eli Jones wrote: > Sodso, > > The phrase "Entity Group" refers to a specific case where two entities from > different db.Model classes are related (one is the parent of the other). > > If you just create a regular db.Model like t

[google-appengine] Re: Datastore Advice

Thanks Nick!! So to make sure I understand: In the last step of your process for getting a list of unread articles, I'd first get the 'UserArticle' entities marked as Unread, and I'm assuming each UserArticle entity would contain the key for the actual article entity. So I'd get the Unread UserA

[google-appengine] Re: Datastore Advice

Thanks again Nick! That helps a lot and I really appreciate it! I watched Brett's Google IO video and what you suggest sounds very efficient. I have to study up on keys a little to make sure I understand how to achieve: "the key name of the UserArticle could be the same as the key name of the ar

Re: [google-appengine] Re: datastore advice?

There are no "tables" on App Engine, only Kinds which are arbitrary collections of properties. In fact, all applications' entities are stored in a single bigtable "table." Entity groups refers to a logical group of entities that are physically stored together; this allows that group of entities t

Re: [google-appengine] Re: datastore advice?

No. You just create 1 million "Entity Groups". Resulting in 1 million instances of customer records. Reread the answer from Robert. You can view the Bigtable DATASTORE (notice the absence of database, usually associated with tables) as one big hashtable. You have a key that designates an object ins

Re: [google-appengine] Re: datastore advice?

Sodso, The phrase "Entity Group" refers to a specific case where two entities from different db.Model classes are related (one is the parent of the other). If you just create a regular db.Model like this: class myUsers(db.Model): username = db.StringProperty(required=True) age =

Fwd: [google-appengine] Re: datastore advice?

Search your life partner

Re: [google-appengine] Re: Datastore Advice

On Tue, Apr 6, 2010 at 5:47 PM, timwhunt wrote: > Thanks Nick!! > > So to make sure I understand: > > In the last step of your process for getting a list of unread > articles, I'd first get the 'UserArticle' entities marked as Unread, > and I'm assuming each UserArticle entity would contain the k