Home » Search

About GROUP BY

61-70 of 200Refresh
Manual
5

Locking in JPA

update collisions resulting from simultaneous updates to the same data by two concurrent users. Locking ... by another transaction. When using ObjectDB, optimistic locking is enabled by default and fully ... is automatically increased by one. Version numbers are managed internally but can be exposed by defining a version
JDO Doc
5

FetchGroup.DEFAULT

. This category includes members defined in the default fetch group in xml or annotations. Redefining the default fetch group via the API does not affect the members defined by this category. Using this category also sets the fetch-depth for the members in the default fetch group. Since: JDO 2.2
JDO Doc
5

javax.jdo.annotations.FetchGroup

javax.jdo.annotations Annotation FetchGroup Target: Classes Annotation for the fetch group of a class. Corresponds to the xml element "fetch-group". Since: JDO 2.1 String[] fetchGroups Fetch groups to be nested (included) in this fetch group. Fetch groups to be nested (included) in this fetch group
Forum
5

java.lang.NullPointerException when using ORDER BY

== 0)) ORDER BY r.startDateTime DESC If we remove the ORDER BY part, the query completes OK ... : Caused by: java.lang.IllegalStateException: com.objectdb.o.InternalException: Unexpected internal ... more                                                                                           Caused by: com.objectdb.o.InternalException: Unexpected
Forum
5

Mapped By Fetch is very Slow

Well ! I think i pointed out a HUGE performance issue with mapped-by attribute (yeah ... , go the MyEntity class and remove "mapped-by". You obtain 1 second max of query fetch. So my performance issue ... .ALL,mappedBy = "myEntity") // Test by adding / remove "mappedBy" public MyEntityChild getEntityChild
Forum
5

Pre-detach loading: retrieval by navigation not working in if statement

/questions/35359676/java-jpa-objectdb-pre-detach-loading-why-retrieval-by-navigation-and-access ... system a BooleanValue wrapper is ultimately an Element that can be referenced by ID, and meets ... boolean value is not the whole story.   By JVM optimizations I meant JIT Compiler optimizations and not
JDO Doc
5

retrieveAll(pcs, useFetchPlan)

the current fetch group must be retrieved, and the implementation might retrieve more fields than the current fetch group. If the useFetchPlan parameter is false, this method behaves exactly as ... are fetched, and other fields might be fetched lazily by the implementation. If the useFetchPlan parameter
JDO Doc
5

retrieveAll(pcs, useFetchPlan)

the current fetch group must be retrieved, and the implementation might retrieve more fields than the current fetch group. If the useFetchPlan parameter is false, this method behaves exactly as ... , and other fields might be fetched lazily by the implementation. If the useFetchPlan parameter
JDO Doc
5

retrieveAll(useFetchPlan, pcs)

the current fetch group must be retrieved, and the implementation might retrieve more fields than the current fetch group. If the useFetchPlan parameter is false, this method behaves exactly as ... , and other fields might be fetched lazily by the implementation. If the useFetchPlan parameter
Forum
5

Strange behaviour with ORDER BY and IN

Hi, after trying out objectdb for a while now and being quite impressed by its speed and overall performance I noticed a strange behaviour where an ORDER BY - directive isn't executed as ... by a simple member (e.g. a String) being the Entity-ID and, at the same time, filter on this member