Hi Anita. I don't understand your data model -- if you are modeling the
relationship between entities of type A and entities of type B using
entities of type C, why do entities of type A have direct references to
entities of type B and vice versa?
Either way, the reason you're getting this error i
Hi Jason,
I could solve my previous problem. But now i am facing some other
problem with many to many relationship tables.
My schema looks as follows:
TableA ---> TableC <- TableB
which means there is many to many relationship between TableA &
TableB. So i want TableA and TableB primary ke
nope you are right ... it's not useless ... apologies
I *think* the problem is in mapping (conceptually) from a mental RDBMS
model
to a GAE DS model ... where "entity group" might be mistaken for
"table" ...
:)
On Aug 26, 3:02 pm, "Jason (Google)" wrote:
> Why do you indicate that the document
>From the error message, it sounds like the parent isn't getting set
correctly. You'll need to share some of your code in order for me to help
you further -- what does your Release class look like and how are you
persisting it?
- Jason
On Sat, Sep 12, 2009 at 4:36 AM, Anita wrote:
>
> Hi Jason,
Hi Jason,
Our schema looks as follows:
ProductType 1->M Product 1>M Release
Data is inserting into Release table. But while fetching data from
release table i am getting following exception:
Field com.ensarm.server.domain.Release.products should be able to
provide a reference t
Why do you indicate that the documentation is useless? The links I included
above state this quite clearly: two entities will be in separate entity
groups by default, even if they're the same kind. Entity groups DO NOT
collect entities of the same kind. If you need transaction support, you'll
need
h' ... so it would seem that 2 or more entity (instances)
persisted in the same tx cause this error ...
this cannot be so ... how is the mapping from instance to entity
(group) made?
On Aug 25, 2:33 pm, Larry Cable wrote:
> I have exactly the same problem, I instantiate a number of @Entity
I have exactly the same problem, I instantiate a number of @Entity
objects
(all of the same type) persist them, and flush them in the context of
the same
transaction.
Since they are all of the same type, and their are no relationships
(although there is
an @Embedded class/field) I would imagine t
Have you read the documentation on entity groups?
http://code.google.com/appengine/docs/python/datastore/keysandentitygroups.html#Entity_Groups_Ancestors_and_Paths
http://code.google.com/appengine/docs/java/datastore/relationships.html
In JDO/JPA, entity groups are expressed using owned relationsh
