ach rather than have a
> Car kind comprising of each different class.
>
> Thanks for the help so far though!
>
> On Aug 8, 10:44 am, Rolf Aden wrote:
>
>
>
>
>
>
>
> > It seems you are not using the latest sdk version (be something pre
> > 1.5.1?).
It seems you are not using the latest sdk version (be something pre
1.5.1?).
As of release 1.5.1 polymorphic relationships are supported for the
default inheritance strategy in JDO (new-table for the base class, and
superclass-table for all subclasses) and JPA SingleTable. You may want
to change Ca
> 1.x (current is 3.x!) — the list of classes to autoload persistence
> management for is just the class names or fully qualified names (I
> mean, with packages)?
>
> On 5 srp, 15:13, Rolf Aden wrote:
>
>
>
>
&g
Looking at the comment in
org.datanucleus.store.appengine.DatastoreManager.getDatastoreClass()
could lead one to think, there are race conditions related to
initializing the meta-data of persistent classes. Since your problem
occurs only from time to time, it could point to the same direction.
If
Max,
to isolate the problem, can you see your entities ("GiniChat") in the
DataStore Viewer?
Are you experiencing this problem with the development server or with
the application on app engine?
Rolf
On 1 Aug., 02:22, max wrote:
> hello,
>
> I'm facing a problem about the persistence of some of
On 19 Jul., 17:18, Kesava Neeli wrote:
> Hi,
> Any one has suggestions to my issue?
I've tried to reproduce your problem with the appengine-datanucleus
1.0.9 plugin, but with no success.
The following tests are passing. Did I miss something? Can you modify
the test to show what is going wrong
