On Oct 6, 11:38 pm, Jon McAlister <[EMAIL PROTECTED]> wrote: > Agreed that the current computational model is inconvenient, > especially for the case of a single admin doing datastore maintenance. > We are working on some solutions for this, but we have to come up with > something that isolates different apps from eachother, as this is a > shared computing platform, and so we have to be a bit more clever here > to ensure that the most number of people can get the greatest use out > of the system. For instance, I'm assuming you wouldn't be happy if an > admin for another app ran an expensive maintenance job and this > affected the quality of service of your app. That's why we are > concerned about relaxing quotas or deadlines.
You don't have to relax quotas/deadlines. But instead of asking developers to do something like this: http://code.google.com/appengine/articles/update_schema.html ...why not do it on our behalf behind the scenes as a result of an extended query language update command? Sure it may be quite slow and it may not be obvious why, but that's ok. It's the convenience that's important. Amir > > If you have some concrete proposals for what else we should > investigate, please let us know. Also, please take a look at other > people's ideas in the Issue Tracker and rate the ones you like. > > On Oct 6, 11:13 am, Amir Michail <[EMAIL PROTECTED]> wrote: > > > On Oct 6, 2:02 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote: > > > > In general, GQL doesn't provide those operations, as it only support > > > querying currently. > > > > However, through the dataviewer's UI it is possible to update, add, and > > > delete data of a specific entity kind. > > > > In terms of updating model properties, the dataviewer does not support > > > such > > > operations since the datastore design differs here from what you would > > > find > > > in a MySQL-like database. For information on how you can currently > > > achieve > > > such things, it might be helpful to read this > > > article:http://code.google.com/appengine/articles/update_schema.html > > > The "Updating Existing Entities" part looks rather inconvenient. Why > > not provide an easier way to do this by relaxing quotas for db > > maintenance and extending the query language to handle typical > > scenarios? > > > Amir > > > > -Marzia > > > > On Mon, Oct 6, 2008 at 10:54 AM, Amir Michail <[EMAIL PROTECTED]> wrote: > > > > > On Oct 6, 1:40 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote: > > > > > Hi Amir, > > > > > > Have you used the GQL query interface in the admin console ( > > > >http://appengine.google.com/datastore/explorer?&app_id=YOURAPPID)?Didyou > > > > > have something else in mind? > > > > > > -Marzia > > > > > It looks rather limited. What about updating, inserting, deleting > > > > data? Adding, renaming, removing columns? > > > > > Amir > > > > > > On Mon, Oct 6, 2008 at 10:21 AM, Amir Michail <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > Hi, > > > > > > > This would help quite a lot with database maintenance. > > > > > > > I don't think inefficient queries are such a big deal if they are > > > > > > not > > > > > > part of the app and are used rarely. > > > > > > > Amir --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
