Since the datastore doesn't support joins, it's generally advantageous to denormalize your data where possible and use fewer tables than you would in a relational model. It seems fairly unlikely that most data would move nicely from 30 tables into a single one, although it's hard to say without knowing more about your schema. The key is to think about how your data will be used, and try to group together things that will usually need to be used in the same view into the same entity if you can.
On Aug 13, 3:03 am, Jeevan <[email protected]> wrote: > Hi all, > I developing an application on app engine using data store. We had 30 > tables and more numbers of fields in the relational DB (mySql). I want > to deploy it on the google app engine using data store. How can I > implement it using google data store, should I create 30 objects or is > that enough create only one object and create all the fields in only > one object. How I set primary key on multiple keys? Is there any need > to set primary key. I will be using Lucene to search data. > > Thanks in advance. > . -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
