[google-appengine] Datastore design question

2010-06-27 Thread Phil McDonnell
I'm using JDO to connect to the datastore and wondering how I should design my tables. I have users who sign up. Users have items. In the RDMS world I'd have a User table and a Items table and the Items table would have a field of user_id which would join with a primary key in the User table. H

Re: [google-appengine] datastore design for hierarchical data.

2010-04-19 Thread Nick Johnson (Google)
Hi, See my answer to your question on Stack Overflow: http://stackoverflow.com/questions/2662212/database-design-in-google-app-engine/2663049#2663049 In general, please refrain from cross-posting here and on SO, unless you've posted to one and haven't received any satisfactory answers after a rea

Re: [google-appengine] datastore design for hierarchical data.

2010-04-18 Thread Jaroslav Záruba
How about updating all ancestors on task status change? That way you wouldn't need to find all the children. On Sun, Apr 18, 2010 at 2:29 PM, gops wrote: > hi , i am designing a simple project based to do list. the idea is to > define tasks under project ( no workflow - just "task is completed"

[google-appengine] datastore design for hierarchical data.

2010-04-18 Thread gops
hi , i am designing a simple project based to do list. the idea is to define tasks under project ( no workflow - just "task is completed" or not is required. ) in a hirarchial way. i.e. each task has multiple task and that task may have other multiple task. a project can be said to be completed if

[google-appengine] Datastore Design

2009-07-29 Thread Mark Jones
I'm using the AppEnginePatch to get a fairly useful Django implementation. The problem I've run into is that parent/child/ ancestor relationships aren't well supported. I've found a less than pretty workaround for the moment. The link to this discussion is http://groups.google.com/group/app-eng

[google-appengine] Datastore design

2009-06-09 Thread Hugh
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "

[google-appengine] Datastore design ideas

2009-05-12 Thread Hugh
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "

[google-appengine] Datastore design ideas

2009-05-12 Thread Hugh
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "

[google-appengine] Datastore design ideas

2009-05-12 Thread Hugh Phelps
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "

[google-appengine] Datastore design ideas

2009-05-12 Thread Hugh
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "

[google-appengine] Datastore design ideas

2009-05-12 Thread Hugh
I'm looking for some high level ideas on how to design a datastore for a Facebook application. In this app a user can collect widgets. I'd like to be able to show a user lists of the widgets owned by their friends - something like: q = db.GqlQuery("SELECT * FROM Widget WHERE owner IN ( ) and "