Having a unique id that is only a property and not the key of the entity
makes it hard.
Are you generating the ID - is it sequential, or just unique (ie an email
address) if the later, you could reliably use a combination of transactions
and a child entity with a key of the unique id, and the an
Hi guys,
Thank you for your answers.
I do not think I have explained my problem properly though when I read your
answers.
I have a table "order" where I save different information about an order.
The unique id of the order comes from an external system, and I want to
save this unique id for th
I think you've been given some good pointers in the right direction, I'll just
add that you need to read and understand the eventual consistency,
transactional and cross entity group (XG) transaction docs for the datastore.
My guess is based on your question you haven't wrapped your head around
Ok, thank you for your input!
-Louise
Den onsdag den 27. januar 2016 kl. 12.39.54 UTC+1 skrev Louise Elmose
Hedegaard:
>
>
> Hi,
>
> I have an issue with too many entities being created in my GAE datastore.
>
> I have an unique id on an entity (which is not the key in this case), and
> there s
> On Jan 28, 2016, at 7:22 AM, Louise Elmose Hedegaard
> wrote:
>
> Hi guys,
>
> Thank you for your answers.
> I do not think I have explained my problem properly though when I read your
> answers.
>
> I have a table "order" where I save different information about an order. The
> unique id
