Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Engine DataStore API #10

Closed
wonderfly opened this issue Jan 9, 2015 · 5 comments
Closed

App Engine DataStore API #10

wonderfly opened this issue Jan 9, 2015 · 5 comments
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@wonderfly
Copy link
Contributor

From yan...@google.com on August 25, 2011 05:14:56

Reported by szieg...@cloudsherpas.com, Today (97 minutes ago)

Version 1.5.0 Describe the problem. Many GAE/J applications make use of other persistence frameworks or use the low-level API, making both the Enhancement step and the JDO library extraneous. How would you expect it to be fixed? Use the low level API for your persistence calls.

Original issue: http://code.google.com/p/google-oauth-java-client/issues/detail?id=10

@wonderfly wonderfly added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. imported priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Jan 9, 2015
@wonderfly wonderfly self-assigned this Jan 9, 2015
@wonderfly
Copy link
Contributor Author

From yan...@google.com on August 25, 2011 05:25:35

Thanks for the feedback. I agree that for Google App Engine it is ideally better to access the Datastore API directly. We do want to keep the JDO-based implementation for use with other web servers.

Can you give us a sense of how important this is for you? In other words, is it just an inconvenience, or is it a serious burden from using this library? I'm just trying to get a sense of the priority of this issue.

Reference: https://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/package-summary.html

Status: Accepted
Owner: moshe...@google.com
Cc: yan...@google.com rmis...@google.com
Labels: -Type-Defect Type-Enhancement

@wonderfly
Copy link
Contributor Author

From szieg...@cloudsherpas.com on August 27, 2011 03:12:00

Sure. That makes sense of course. It is only an inconvenience as it messes with our Eclipse project build path, adds an unnecessary step to our build (that we can remove), and causes us to maintain a jar that doesn't need to exist for our project otherwise. All this only amounts to a minor annoyance so far.

@wonderfly
Copy link
Contributor Author

From yan...@google.com on December 08, 2011 12:19:27

Owner: yan...@google.com
Cc: -yan...@google.com moshe...@google.com

@wonderfly
Copy link
Contributor Author

From yan...@google.com on February 28, 2012 17:12:26

Status: Fixed
Labels: Milestone-Version1.7.0 Component-OAuth2

@wonderfly
Copy link
Contributor Author

From yan...@google.com on March 12, 2012 12:52:57

Summary: App Engine DataStore API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

1 participant