Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6329115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T17:35:32+00:00 2026-05-24T17:35:32+00:00

I’m making a product review service using Google App Engine, and I’m wondering about

  • 0

I’m making a product review service using Google App Engine, and I’m wondering about good practice for structuring my datastore models (I’m using the “high replication” setting, and I’ve gathered that the way you structure entities and their ancestors is quite important). Particularly, I’m wondering about using lists of keys (or if I should be using ancestors/parents instead). My basic model looks like this:

-------------        
-  Product  -
-------------       ----------
- [reviews] - ----> - Review -
-           -    /  ----------       -------------
-------------   |   - author - --->  -   User    -
                |   -        -       -------------
                |   ----------       - [reviews] - --|
                |                    -           -   |
                |                    -------------   |
                |                                    |
                --------------------------------------

As you can see, each product contains a list of reviews, and each user account also contains a list of reviews written by the user. My main questions are about these lists of reviews and whether it’s best to store them as lists of review keys, or whether it’s better to just generate them on the fly using queries.

It seems that for the list of reviews related to a given product, the best thing to do might be to create the Review entities as children of the given Product, and then just create the list of reviews on-the-fly when I need it using an ancestor query, e.g.:

reviews = db.GqlQuery("SELECT * "
                      "FROM Review "
                      "WHERE ANCESTOR IS :1 "
                      "ORDER BY date DESC LIMIT 10",
                       product_key)

However, for getting a list of reviews written by a given user, I can’t think of a way to do the same as above. It seems I would have to store a list of keys that pertain to each review the user has written. Is this correct? If so, what’s the best way to store a list of keys in GAE datastore?

Any help or insight into this scenario as it relates to GAE datastore and/or general database design would be greatly appreciated. I’m pretty new to database design in general, so the more help the better. Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T17:35:34+00:00Added an answer on May 24, 2026 at 5:35 pm

    I would suggest doing neither – instead, use foreign keys. If the Review has a db.ReferenceProperty to the product it’s for and the user who wrote it, you can easily fetch all the reviews for a product (Product.review_set.all()), all the reviews a user has written (User.review_set.all()), and the product and user for a review.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm making a simple page using Google Maps API 3. My first. One marker
I am reading a book about Javascript and jQuery and using one of the
We're building an app, our first using Rails 3, and we're having to build
I am using Paperclip to handle profile photo uploads in my app. They upload
link Im having trouble converting the html entites into html characters, (&# 8217;) i
That's pretty much it. I'm using Nokogiri to scrape a web page what has
I have a string like this: La Torre Eiffel paragonata all’Everest What PHP function
I'm using v2.0 of ClassTextile.php, with the following call: $testimonial_text = $textile->TextileRestricted($_POST['testimonial']); ... and
I'm parsing an RSS feed that has an ’ in it. SimpleXML turns this
We are using XSLT to translate a RIXML file to XML. Our RIXML contains

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.