Hi Christophe,
The only guarantee when you use allocateIds() is that the ids you receive
have not yet been assigned as auto ids or by previous calls to
allocateIds().
As Vinny P says, you cannot reset the id sequence. Also, we have not yet
switched to 'scattered' ids in production-- you can see what those look
like in the dev appserver where it is the default. They are large numbers.
The discontinuities you see now are due to ids being drawn from different
batches which we cache for performance, so even under the current
production id policy, it's quite likely that you will see a sequence such
as 1, 2, 1001, 2001, 3, 4, 2002, 1002, etc.
If you'd like to precisely control what your keys look like, you can use
named keys.
-Jesse Rohwer
Google App Engine
On Wednesday, May 15, 2013 6:43:34 AM UTC-7, Christophe Pruvost wrote:
>
> Hi all,
>
> I deploy my application then I use Id Allocation and get a range from
> Club(1) To Club(10)
>
> I redeployed my application then I use Id Allocation and get a range from
> Club(1001) To Club(1010)
>
> So my question : what is the expected behavior for id allocation ? please
> give some details....
>
> Each time I redeploy the I increase the sequence by 1000 ?
>
> I want to flush the Club Data so I would like to get a new Sequence
> beginning from Club(1)...is it possible to do that ? What kind of action
> could I have on this sequence generator ...I do not find information on
> that ?
>
> Thank you for all
>
> Christophe.
>
> PS : My code : KeyRange keyRangeClub = datastore.allocateIds("Club", 10);
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
