ObjectDB Database Search

are also identical (shared) if defined in the persistence.xml in the CoreEJB module. If SpecWeb1

objects have identity and support multiple references without duplication. All the other types

management of identity ) are built-in to JDO.  We have recently migrated projects for JPA

Hi, we have a strange performance problem with ObjectDB 2.5.3_01 and JBoss 7.1.1. We have two ObjectDB databases on one ObjectDB server. Production database is running 5-10 times slower than test database. Their size and number of records are almost identical . When running production database in

far as I can tell, my unit test is pretty much identical . Not sure why this doesn't work. Thanks

The DB Explorer cannot be opened after schema package renaming of entity types because it seems that deprecated entity types which are removed from our java project break the database. In the database the entity types and deprecated entity types can be part of the identical package. The schema

I don't think JDO supports altering an entity's Application Identity .  Does ObjectDB? @PersistenceCapable public class MyClass implements Serializable, Cloneable{ @Id private StringIdentity id; ... }   PersistenceManager persistenceManager = ...; Transaction transaction

a (potentially identical ) new value? kjkrum Kevin The behavior is different for enhanced classes and non

(strategy=GenerationType. IDENTITY ) Should I remove the whole db? TIA gzdillon Lai Yang Adding 

; } A possible solution: Avoid multiple Attribute instances with identical type / value by defining a composite

Player { @Id @GeneratedValue(strategy = GenerationType. IDENTITY ) public int id; @Temporal(TemporalType

both options (in production) and then choose the better one. The two options are not identical . ObjectDB uses

for primary key: @Id @GeneratedValue(strategy=GenerationType. IDENTITY ) private String ID; kiki

be so ? Why aren't the 2 enhancement techniques giving identical data access results ? webel Dr Darren Kelly

that your classes on all the clients are identical . support Support Here is the output from the Doctor

you can only set the backup parent folder, the name of the backup file is identical to the name

Hello, it is possible to recover an entity that has been removed automatically by CascadeType.Remove. After cascade remove the removed entity will be persisted with the identical primary key. Are all broken references in other entities on this removed/persisted entity repaired again? best regards

both the strategy and the generator attributes of the @GeneratedValue annotation. By using the IDENTITY

both plugins are identical . I checked all of this with a debugger.   We had a similar issue last year 2015

;consequences of not having an identity for embedded objects. Sharing persistent objects is only possible with entity objects. support Support

. IDENTITY )     private long id;     private String name;   

identity , the outcome of the merge operation is undefined. Some providers might allow the managed

, although the relevant if statement is apparently identical . It has taken me ages to finally find

; @Id @GeneratedValue(strategy = GenerationType. IDENTITY ) @Basic(optional = false) @Column(name = "id

Hi! I'm trying to compare 2 identical objects in SELECT with no success: @Embeddable public class PhoneNumber implements Serializable {     int countryCode;     long number;   Which is a part of Customer object: @MappedSuperclass @NamedQueries({    

{ private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType. IDENTITY

are not identical . However, enhanced classes are much more efficient in performance and in memory

because the size of the arrays is identical to the cache page configuration. We use the ObjectDB as

. Embeddable classes, however, do not have an identity (primary key) of their own which leads to some

which hold much memory, if we execute several transactions on the identical entity manager

identical with the TCVector interface of main database). We executed a query on the main database

at a debug break point. We steps over the next statement which also executes the identical query