thanks. dose put() for add new or for edit take same ops? to edit may alter the property indexed or not indexed.
if the entity has 2 indexes, one put() will take 5 ops in sum, right? how many will i save in using the keys_only than fetching the entity? On 9月4日, 上午3时30分, Philip <[email protected]> wrote: > You have to consider the following points: > > - put() > Each property the entity has will add at least 2 extra write ops if > the property is indexed (for asc and desc order) > > - fetch() > Don't use the offset property; you will be charged for > (number_of_items + offset) read ops. If you need paging you have to > use cursors. > > - all() > Does cost nothing because it does not interact with the datastore. If > you only need the keys of the entity's you should use the keys_only > argument. > > I hope that helps. > > On Sep 3, 5:07 pm, saintthor <[email protected]> wrote: > > > > > > > > > how about these funtions? i use these. > > > Model.put() .get() .fetch() .count() .gql() .all() > > > On 9月3日, 下午10时08分, Philip <[email protected]> wrote: > > > > Provide some example code. > > > > On Sep 3, 3:53 pm, saintthor <[email protected]> wrote: > > > > > today, till now, one of my apps get 1888 requests and 41090 datastore > > > > api calls. i think the api calls should not be so many. -- 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.
