 1 | loads properly, so I put the ObjectDB points tutorial (exported) jar into my current web app, and I created a Point object successfully in code. So I think objectdb.jar is getting loaded alright |
1 | Hi, I've never used an OODB, I'm looking for a starting point but a recurrent concern is the Data Portability one. More clear: what options / strategies do I have to export / move my data to another tool, if there is a need to? One key point of Ojectdb (as far as I had read) is Code Portability |
1 | this problem. Hopefully a fix will be released soon. To the methodenstreit, I do insist on pointing ... . This can be relative to Fat client or thin client problem. I believe since a client points the problem |
1 | to point to managed versions of the entities referenced by the detached entity. If the entity ... is undefined. Some providers might allow the managed copy to point to the non-persistent object |
1 | ();
emf.close();
}
} I cannot/don't know how to remove external dependencies at this point since I ... (unknown to me) and doesn't always get removed when the application is terminated. At no point do I |
1 | get the point. I ask a way to subquery in #1. You suggest splitting it into two query in #2. I ... ) Then you doubt the relation between #1 and #3 !!!!!! Indeed I don't get the point since in #3 there is no GROUP BY / HAVING. gzdillon |
1 | /api/user/siegfried I had tried that previously and failed set a break point and failed to notice ... my break point! Hurray! I think the problem is that it does not know how to convert the guest object |
1 | this year. Great news. Does this plan also include the possibility to choose a restoration point ... among a few restoration points from a backup. The Replayer can also be run up to a specified transaction, e.g |
1 | to be releasing a trial version of this product in a few weeks, at which point we will be wanting to buy ... to reproduce the exception? The other thread does not use ObjectDB at the point at which it crashes |
1 | May I just point out something screamingly obvious. Your own JavaEE example has a single entity ... of query need not be managed (that it is a provider variation point). - the one line of code your approach |
