About table

forum_thread

Help with 'not like/lower' query

Hi again,   Honestly, I'm fairly new with JPA2 Criteria queries - but as far as code effort goes, it has saved me a bit of pain. I'm writing a dynamic query builder (only 1 level deep for basic entities) - but  even though I get most queries to work, I am getting the following error. This is using Criteria with a combination of LOWER/UPPER - NOT LIKE: ... count (with a subsequent fetch of a page of 20 results per table view on the UI) where a user belongs to a company, and the lower case ...

 
api-jdo

Joins.value

The join definitions used for the mapping of this type.(Annotation Element of javax.jdo.annotations.Joins)

 
issue

Out of Memory - Slow leak?

This is a continutaion of Issue 61 - unfortunately it doesnt seem that the fix in 2.2.9_03 has fixed the problem. The scenario is still the same: I have two "producer" processes which insert messages into an objectdb "queue" database running with an objectdb server process. I have one "consumer" process which reads messages from the queue database and inserts these into an embedded "normal" objectdb database. This is the process which has generated the OOM exception. Bug Version: 2.2.9 Priority: Normal Status: Fixed Replies: 13 Type:  Bug ...

 
release

2.7.0

... Fixed a bug in using @TableGenerator / GenerationType.TABLE. Fixed handling classes with no persistent fields in new ... when a field in a summary view is not included in the tree/table view. Fixed a bug in caching Criteria query programs with ...

 
release

2.7.1

... Fixed a bug in using @TableGenerator / GenerationType.TABLE. Fixed handling classes with no persistent fields in new ... when a field in a summary view is not included in the tree/table view. Fixed a bug in caching Criteria query programs with ...

 
forum_thread

@JoinColumn(nullable=false)

  During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the following: #1 2011-08-01 20:44 During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the ...

 
api-jpa

javax.persistence.Id

Specifies the primary key of an entity.(Annotation of JPA)

 
forum_thread

Is it possible to commit only specific elements?

Hello, As stated above, I would like to know if it is possible to commit only specific elements, or at least update a single table, disregarding the other entities loaded in the persistency context? I have a complex hierarchy of intertwined objects. Currently I am clearing my persistency context, retrieving only the needed ones, creating new ones (which I want to commit), detaching the ones I've previously retrieved and finally committing. My context is big data and performance is an issue.      ... commit only specific elements, or at least update a single table, disregarding the other entities loaded in the persistency context? ...

 
api-jpa

javax.persistence.ElementCollection

Defines a collection of instances of a basic type or embeddable class.(Annotation of JPA)

 
forum_thread

Failing to read entities under load in multithreaded tests

Hi, We are experiencing an issue in our application that only occurs under load - we sometimes fail to read entities from the database. ... ( strategy = InheritanceType . TABLE_PER_CLASS ) @ TableGenerator ( name = ... ( strategy = GenerationType . TABLE , generator = "TestIdTableGen" ) public long ...