[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Yep, many to many relationships work well. They can also be
polymorhic and use inheritance with no problems.
On May 3, 12:09 am, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I have looked at twig, I liked it a lot, but there is one issue about many
to many relationships. Does Twig support them?
Sincerely,
Michael Shtelma
On Sun, Mar 28, 2010 at 5:25 PM, John Patterson jdpatter...@gmail.comwrote:
There are alternatives: Twig, Objectify, SimpleDS, Slim3, Siena. Take your
pick and get your app working today.
On 28 Mar 2010, at 21:47, Trung wrote:
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA
model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not
yet
supported.
and your class hierarchy resembles the one above, you can disable this
check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
On May 2, 2:40 pm, jtuchscherer jtuchsche...@gmail.com wrote: John, are you saying that Twig, Objectify, SimpleDS, Slim3 and Siena don't have this problem? I can only definitivly speak for Twig but I am certain that the others also would not suffer this problem or many many of the other issues with JDO-GAE. If yes, which one can you recommend? Well as founder of Twig I would of course recommend it! :) However, the other projects all have strengths which you might want to look into. Comparing Twig with the other non-standard datastore interfaces I would say it has a slightly higher level of abstraction which has the advantage of making your code simple at the cost of being less aware of when each peice of data is loaded. I am a little bit reluctant to use anything that makes your code tied to GAE. The beauty of JDO/JPA is that I can use the same code and deploy anywhere else. I think you will find that this is not an easily achievable goal. But if that is my only option to get around this limitation I probably would use Twig, Objectify ... You will certainly save yourself a LOT of time and grey hairs. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hi,
do you have some sort of example or tutorial for the many to many relations
?
When I have tried using them, I got really strange exception.
Twig was not able to determine the key for some dependent entities...I think
I was doing smth wrong...
I will describe the problem in with more details a little bit later...
Sincerely,
Michael Shtelma
On Mon, May 3, 2010 at 12:46 PM, jd jdpatter...@gmail.com wrote:
Yep, many to many relationships work well. They can also be
polymorhic and use inheritance with no problems.
On May 3, 12:09 am, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I have looked at twig, I liked it a lot, but there is one issue about
many
to many relationships. Does Twig support them?
Sincerely,
Michael Shtelma
On Sun, Mar 28, 2010 at 5:25 PM, John Patterson jdpatter...@gmail.com
wrote:
There are alternatives: Twig, Objectify, SimpleDS, Slim3, Siena. Take
your
pick and get your app working today.
On 28 Mar 2010, at 21:47, Trung wrote:
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the
types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or
JPA
model
objects has two relationship fields of the same type. For
example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is
not
yet
supported.
and your class hierarchy resembles the one above, you can disable
this
check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google
Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
google-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%252bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google
Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
google-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%252bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group athttp://
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
On May 4, 12:02 am, Michael Shtelma mshte...@gmail.com wrote: When I have tried using them, I got really strange exception. Twig was not able to determine the key for some dependent entities...I think I was doing smth wrong... Ah yes, when you have circular references and you use auto generated (default) keys you will need to store those items first. For more details we can discuss further on the Twig discussion group. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Thank you, yes, now I have found out this too :))) I had just to do some more experiments Twig is working great with many to many relationships, I will defenitely use it :)). Sincerely, Michael Shtelma On Tue, May 4, 2010 at 12:05 AM, jd jdpatter...@gmail.com wrote: On May 4, 12:02 am, Michael Shtelma mshte...@gmail.com wrote: When I have tried using them, I got really strange exception. Twig was not able to determine the key for some dependent entities...I think I was doing smth wrong... Ah yes, when you have circular references and you use auto generated (default) keys you will need to store those items first. For more details we can discuss further on the Twig discussion group. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Sorry to revive this old topic, but I still see this problem in
1.3.3.1
I get it in the following scenario:
class Parent {}
class Child {
private Key id;
private Parent mother;
private Parent father
}
Error message:
Child has multiple relationship fields of type Parent: father and
mother. This is not yet supported.
John, are you saying that Twig, Objectify, SimpleDS, Slim3 and Siena
don't have this problem? If yes, which one can you recommend? I am a
little bit reluctant to use anything that makes your code tied to GAE.
The beauty of JDO/JPA is that I can use the same code and deploy
anywhere else. But if that is my only option to get around this
limitation I probably would use Twig, Objectify ...
Thanks,
Johannes
On Mar 28, 9:25 am, John Patterson jdpatter...@gmail.com wrote:
There are alternatives: Twig, Objectify, SimpleDS, Slim3, Siena. Take
your pick and get your app working today.
On 28 Mar 2010, at 21:47, Trung wrote:
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the
types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO
or JPA model
objects has two relationship fields of the same type. For
example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so
the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This
is not yet
supported.
and your class hierarchy resembles the one above, you can
disable this check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google
Groups Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com
.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com
.
For more options, visit this group
athttp://groups.google.com/group/google-appengine-java?hl=en
.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hi all,
I have looked at twig, I liked it a lot, but there is one issue about many
to many relationships. Does Twig support them?
Sincerely,
Michael Shtelma
On Sun, Mar 28, 2010 at 5:25 PM, John Patterson jdpatter...@gmail.comwrote:
There are alternatives: Twig, Objectify, SimpleDS, Slim3, Siena. Take your
pick and get your app working today.
On 28 Mar 2010, at 21:47, Trung wrote:
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA
model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not
yet
supported.
and your class hierarchy resembles the one above, you can disable this
check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA
model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not
yet
supported.
and your class hierarchy resembles the one above, you can disable
this check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
There are alternatives: Twig, Objectify, SimpleDS, Slim3, Siena. Take
your pick and get your app working today.
On 28 Mar 2010, at 21:47, Trung wrote:
Hi GAE team,
Any workarounds for this issue?
Thanks
On Feb 14, 8:55 am, Payam pmoghad...@gmail.com wrote:
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the
types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO
or JPA model
objects has two relationship fields of the same type. For
example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so
the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This
is not yet
supported.
and your class hierarchy resembles the one above, you can
disable this check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google
Groups Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com
.
To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com
.
For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en
.
--
You received this message because you are subscribed to the Google Groups Google
App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
The problem is still not solved.
Although you can persist an object with multiple relations of the
same type. When you actually query the object, the retrieved object
has duplicates for the multiple relations.
As in, if I were to persist instances A, B inside C. When I query for
C, both objects retrieved will be A. There will be no B.
This is a serious bug!
On Jan 26, 4:54 pm, oth other...@gmail.com wrote:
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA
model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not
yet
supported.
and your class hierarchy resembles the one above, you can disable this
check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not yet
supported.
and your class hierarchy resembles the one above, you can disable this check
by with the following config property:
property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Michael,
In your jdoconfig.xml file add this entry:
property
name=datanucleus.appengine.allowMultipleRelationsOfSameType
value=true/
Thanks
On Jan 26, 3:12 pm, Michael Shtelma mshte...@gmail.com wrote:
Hi all,
I am also experiencing this problem on GAE 1.3.0.
Using multipleRelationsOfSameTypeAreErrors helps not in all cases,
when I am trying to read such entities I get mentioned exception.
Are the any solution for the 1.3.0 ?
Thanks,
Michael
On Jan 21, 9:20 am, cowper iamco...@gmail.com wrote:
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA
model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not yet
supported.
and your class hierarchy resembles the one above, you can disable this
check
by with the following config property:
property
name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hi,
I have a similar issue with 1.3.0 however it arises when the types
are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround
valid for 1.3.0?
thx,
Conor
On Dec 4 2009, 9:52 pm, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not yet
supported.
and your class hierarchy resembles the one above, you can disable this check
by with the following config property:
property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
One more thing- I get this error the first time I hit this code after
idling or starting up, but subsequent runs work ok.
Dan
On Sat, Jan 16, 2010 at 2:51 AM, Daniel Benamy dben...@gmail.com wrote:
I think I'm hitting this check since updating to 1.2.8. I've got
something like:
class A {
B bVar;
ListB bList;
}
Should I be getting this error? I haven't noticed a problem with my
app using this setup.
Thanks!
Dan
On Dec 5 2009, 12:52 am, Max Ross (Google) maxr
+appeng...@google.com wrote:
SDK 1.2.8 contains a new check that detects if one of your JDO or JPA model
objects has two relationship fields of the same type. For example:
class A {
ListB bList;
ListB anotherBList;
}
Unfortunately I was a little too aggressive with this check, so the
following also run afoul of the check:
abstract class B {}
class C extends B {}
class D extends B {}
class A {
ListC cList:
ListD dList;
}
If you get an exception that says
Class XXX has multiple relationship fields of type . This is not yet
supported.
and your class hierarchy resembles the one above, you can disable this check
by with the following config property:
property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors
value=true/
We'll get this fixed shortly.
Sorry for the trouble,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Datastore cursors is something we hoped to support in 1.2.8 but it didn't quite make it in. There are changes in the ORM code to support it but it's not actually enabled in the datastore back-end. This should be available early next year. On Sat, Dec 12, 2009 at 7:46 AM, David Fuelling sappe...@gmail.com wrote: Thanks Max, that fixed my problem with the inheritence. One other question: What version of the ORM code is currently included in the 1.2.8 SDK? I only ask because I noticed that the release notes for ORM VERSION 1.0.4 Final includes Support datastore cursors, and am wondering if that is actually working or still a pre-release item (didn't see anything in the docs about it). Thanks! david On Dec 10, 11:24 pm, Max Ross (Google) maxr+appeng...@google.commaxr%2bappeng...@google.com wrote: I've made a backwards-compatible bug fix release candidate available athttp://code.google.com/p/datanucleus-appengine/downloads/list The release contains a fix for this issue and also renames the config property to datanucleus.appengine.allowMultipleRelationsOfSameType Max -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Thanks Max, that fixed my problem with the inheritence. One other question: What version of the ORM code is currently included in the 1.2.8 SDK? I only ask because I noticed that the release notes for ORM VERSION 1.0.4 Final includes Support datastore cursors, and am wondering if that is actually working or still a pre-release item (didn't see anything in the docs about it). Thanks! david On Dec 10, 11:24 pm, Max Ross (Google) maxr+appeng...@google.com wrote: I've made a backwards-compatible bug fix release candidate available athttp://code.google.com/p/datanucleus-appengine/downloads/list The release contains a fix for this issue and also renames the config property to datanucleus.appengine.allowMultipleRelationsOfSameType Max -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Hmm...looks like I'm not using @MappedSuperclass in my abstract parent class. I'll give that a try and see if it fixes things. On Dec 9, 8:27 pm, David Fuelling sappe...@gmail.com wrote: Thanks Max! Just updated to 1.2.8 and ran into this problem. The workaround looks good, though I think you specified the boolean value wrong if you want to disable this error. Should be: property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors value=false/ In my case, the app builds fine with no Enhancer errors or warnings. However, when I run my app, I'm get the following error when I try to load entities that extend an abstract baseclass: javax.persistence.PersistenceException: PersistentclassXXXdoes not seem to have been enhanced. XXX is an abstractclasssimilar to your Bclassabove. Any ideas? My abstractclassis not marked as an Entity. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
I've made a backwards-compatible bug fix release candidate available at http://code.google.com/p/datanucleus-appengine/downloads/list The release contains a fix for this issue and also renames the config property to datanucleus.appengine.allowMultipleRelationsOfSameType Max On Thu, Dec 10, 2009 at 9:55 AM, David Fuelling sappe...@gmail.com wrote: Hmm...looks like I'm not using @MappedSuperclass in my abstract parent class. I'll give that a try and see if it fixes things. On Dec 9, 8:27 pm, David Fuelling sappe...@gmail.com wrote: Thanks Max! Just updated to 1.2.8 and ran into this problem. The workaround looks good, though I think you specified the boolean value wrong if you want to disable this error. Should be: property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors value=false/ In my case, the app builds fine with no Enhancer errors or warnings. However, when I run my app, I'm get the following error when I try to load entities that extend an abstract baseclass: javax.persistence.PersistenceException: PersistentclassXXXdoes not seem to have been enhanced. XXX is an abstractclasssimilar to your Bclassabove. Any ideas? My abstractclassis not marked as an Entity. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Class XXX has multiple relationship fields of type YYYY
Thanks Max! Just updated to 1.2.8 and ran into this problem. The workaround looks good, though I think you specified the boolean value wrong if you want to disable this error. Should be: property name=datanucleus.appengine.multipleRelationsOfSameTypeAreErrors value=false/ In my case, the app builds fine with no Enhancer errors or warnings. However, when I run my app, I'm get the following error when I try to load entities that extend an abstract base class: javax.persistence.PersistenceException: Persistent class XXX does not seem to have been enhanced. XXX is an abstract class similar to your B class above. Any ideas? My abstract class is not marked as an Entity. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
