Hello, I'm just here because i feel i need to rant a little. I came here expecting way too much. I'm of course blaming me for being way too optimistic but i also believe ranting against google is somehow justifiable, and i'll explain why.
I've started porting an application on Google App engine and i'm now sick of discovering exceptions like : - Detected attempt to establish PictureThread(28) as the parent of Picture(27) but the entity identified by Picture(27) has already been persisted without a parent. A parent cannot be established or changed once an object has been persisted - cannot operate on two differents types of entities in the same request/transaction'. Your documentation has headed me in the wrong direction; all you mention is 'unowned relationships' and 'many-to-many relationships' are not supported. Please fix that. Give us the real limitations on the documentation! There is no mention of "one to one" limitations or 'handling multiple entities in same transaction' limitations anywhere. It would totally be understandable not to mention theses limitations when JDBC APIs were created, but nowadays, when you mention 'JPA', this kind of limitations HAVE to be mentionned. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
