Hi Ryan,
posting to the group since it could be interesting for others, as you suggested.
On Sun, Mar 8, 2009 at 12:26 AM, Ryan Barrett wrote:
> On Sat, 7 Mar 2009, Waldemar Kornewald wrote:
>
>> is there a reason why entities can have a key id or a key_name? Would
>> it be so much less efficien
Waldemar Kornewald wrote:
>
> I'm not against key ids in general. The problem with ids in App Engine
> is that they can't be set manually which means backups become much
> more difficult and when restoring a backup (or converting data from
> SQL) URLs have to be changed (because the id can't be re
> we'd love to provide operations for advanced users to manage the id
> namespace, e.g. NextId(), SetNextId(), and ReserveIds(), which would all take
> a root entity as their argument.
I assume that one of those operations allows programmers to assign the
id to a db.Model instance for a new ent
Hi Ryan,
On Mar 9, 1:23 am, ryan wrote:
> > Couldn't you allow for overriding ids while at the same time assigning
> > free ones automatically?
>
> definitely! we've considered this internally for a while. we'd love to
> provide operations for advanced users to manage the id namespace, e.g.
> Ne
On Mar 8, 6:28 pm, Andy Freeman wrote:
>
> I assume that one of those operations allows programmers to assign the
> id to a db.Model instance for a new entity.
On Mar 9, 4:29 am, Waldemar Kornewald wrote:
>
> ID management is by far not as important as being able to set custom
> ids. Could you
