Google app engine ReferenceProperty relationships

前端未结

关注

 4  1249

I\'m trying to get my models related using ReferenceProperty, but not have a huge amount of luck. I have 3 levels: Group, Topic, then Pros, and Cons. As in a Group houses ma

相关标签:

4条回答

攒了一身酷

2021-01-07 08:04
I'm not quite sure what problem you're having. Everything you list looks fine - the ReferenceProperties are set up according to what one would expect from your dscription. The only problem I can see is that in your template, you're referring to a variable "topics", which isn't defined anywhere, and you're not iterating through the topics for a group anywhere. You can do that like this:
```
<html>
 <body>
 <a href="/newgroup">New Group</a>
 
 {% for group in groups %}

 {{ group.group_name|escape }} by {{ group.group_user }} at {{ group.group_date }} {{ group.raw_id }}
 
 <a href="/newtopic?id={{group.key.id}}" >New topice </a>
 
 Topics:
 <ul>
 {% for topic in group.topics %}
 <li>{{topic.topic_name}}</li>
 {% endfor %}
 </ul>
 {% endfor %}
 </body>
</html>
```
To create a new topic, just use the constructor, passing in the required arguments:
```
mytopic = Topic(topic_name="foo", topic_group=somegroup)
```
Here, somegroup should be either a Group object, or a key for a Group object.
0 讨论(0)
发布评论:

提交评论
- 加载中...
北海茫月

2021-01-07 08:05
Something that has side effects, such as altering the store (by creating a new object for example) should NOT be an HTTP GET -- GET should essentially only do "read" operations. This isn't pedantry, it's a key bit of HTTP semantics -- browsers, caches, proxies, etc, are allowed to act on GET as read-only operations (for example by caching results and not passing a request to the server if they can satisfy it from cache).

For modifications, use HTTP verbs such as POST (most popular essentially because all browsers implement it correctly) or for specialized operations PUT (to create new objects) or DELETE (to remove objects). I assume you'll be going to use POST to support a variety of browsers.

To get a POST from a browser, you need either Javascript wizardy or a plain old form with method=post -- I'll assume the latter for simplicity.

If you're using Django 1.0 (which app engine supports now), it has its own mechanisms to make, validate and accept forms based on models. Other frameworks have their own similarly advanced layers.

If you want to avoid "rich" frameworks you'll have to implement by hand templates for your HTML forms, direct them (via some kind of URL dispatching, e.g. in app.yaml) to a handler of yours implementing with a def post(self):, get the data from the request, validate it, form the new object, put it, display some acknowledgment page.

What part or parts of the procedure are unclear to you? Your question's title focuses specifically on reference properties but I'm not sure what problem they are giving you in particular -- from the text of your question you appear to be on the right tack about them.

Edit: the OP has now clarified in a comment that his problem is how to make something like:
```
"<a href="/newtopic?id={{group.key.id}}" >New topic </a>" 
```
work. There's more than one way to do that. If the newtopic URL is served by a static form, the handler for the post "action" of that form could get back to that id= via the Referer: header (a notorious but unfixable mis-spelling), but that's a bit clunky and fragile. Better is to have the newtopic URI served by a handler whose def get gets the id= from the request and inserts it in the resulting form template -- for example, in a hidden input field. Have that form's template contain (among the other fields):
```
<INPUT TYPE=hidden NAME=thegroupid VALUE={{ theid }}> </INPUT>
```
put theid in the context with which you render that template, and it will be in the request that the def post of the action receiving the form finally gets.
0 讨论(0)
发布评论:

提交评论
- 加载中...

春和景丽

2021-01-07 08:12

Just to answer the question for others as you probably figured this out:

class NewTopic(webapp.RequestHandler):
    def get(self):
      groupId = self.request.get('group')
      # either get the actual group object from the DB and initialize topic with topic_group=object as in 'Nick Johnson's answer, or do as follows
      topic = Topic()
      topic.name = self.request.get("topicname")
      topic.reference = groupId
      topic.put()

0 讨论(0)

情书的邮戳

2021-01-07 08:22
Thankyou for the reply.

Yeah I am aware of the get vs post. The class I posted was just to actually print all the Groups().

The issue I have is I'm unsure how I use the models to keep data in a sort of hierarchical fashion, with Groups > Topics > Pros/Cons.

Grabbing data is simple enough and I am using:
```
class NewGroupSubmit(webapp.RequestHandler):
    def post(self):

        group = Groups()
        if users.get_current_user():
            group.group_user = users.get_current_user()     
        group.group_name = self.request.get('groupname')

        group.put()
        self.redirect('/summary')
```
I need another function to add a new topic, that stores it within that group. So lets say a group is "Cars" for instance; the topics might be "Ferrari", "Porsche", "BMW", and then pros/cons for each topic. I realise I'm being a little vague, but it's because I'm very new to relational databasing and not quite used to the terminology.
0 讨论(0)
发布评论:

提交评论
- 加载中...