Thanks for this information but I'm little bit confuse about ancestors As read from document and search is that ancestors are used for transactions and every ancestors are
-- in same entity groups and entity groups store in same datastore node which make it low scale able is it right ?
Creating User as a parent of posts and posts are parent of comments is good ?
Rather than this we can add one extra property in posts Entity like user_id as shown in example and filter it using property.
Which is good and scale able filter posts by ancestors or add extra property user_id in posts Entity and filter by property ?
I know both condition get same results but I want to know which one is good in performance and scale ?
Sorry, I'm new in datastore
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/f3a1c19d-8adc-4ea3-adb7-4d15c485e897%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment