ociule / gae-datastore
- Source
- Commits
- Network (0)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Branch:
master
Want to use just the datastore from the AppEngine stack? This will give you a web hash-value gateway to the datastore.
| name | age | message | |
|---|---|---|---|
 |
README | Wed Feb 18 09:12:55 -0800 2009 | |
| |
app.yaml | Sun Feb 15 14:26:07 -0800 2009 | |
| |
baseHandler.py | Sun Feb 15 14:26:07 -0800 2009 | |
| |
getHandler.py | Sun Feb 15 14:26:07 -0800 2009 | |
| |
index.yaml | Sun Feb 15 14:26:07 -0800 2009 | |
| |
main.py | Sun Feb 15 14:26:07 -0800 2009 | |
| |
putHandler.py | Sun Feb 15 15:32:18 -0800 2009 | |
| |
record.py | Sun Feb 15 14:26:07 -0800 2009 | |
 |
templates/ | Sun Feb 15 14:29:32 -0800 2009 |
README
Want to use just the datastore from the AppEngine stack? This will give you a web hash-value gateway to the datastore. h2. Really **simple** to use! To **store** a value, just post it to /put/_key_ as the _value_ parameter. * The key is optional, a random one will be generated for you if missing (you'll get it back in the answer). * Due to AppEngine datastore limitations, the key must start with a letter. * Alternatively, post the key in a _key_ Post parameter. If you do both (key in URL and Post), the URL takes precedence. * If the key already exists, the value will be updated. To **fetch** a value, just make a Get request to /get/_key_ h2. Just a key-value store ? Yes, but a fast and scalable one. As scalable as App Engine. h2. Roadmap * True JSON support including GQL queries and aggregates would be nice. * Somehow expose all datastore functionality through a Rest interface.
