ObjectDB ObjectDB
Home » Forum » mismatch after Enum changes

mismatch after Enum changes

#1
luca.cameriniluca.camerini
Joined on 2015-06-26

Hi,

I have an entity, an attribute is a enum type: 

public enum MyEnum {
  AA, BB, CC, DD;
}

I populated the database, than I changed the enum types deleting some unused types (es. AA) without reset database:   

public enum MyEnum {
  BB, CC, DD;
}

Now there are mismatches with enums in database. It looks as if objectdb keeps the "position" of enum. For example: attributes of entity set to ENUM.BB (second position before the change) now are set to ENUM.CC (second position after the change).

It is a correct behaviour?

Thanks in advance!

✂
edit
delete
#2
supportsupport
Joined on 2010-05-03

Yes, this is the default behavior. Enum values are stored as ordinal number by default, and then you must preserve the position of every existing value.

Alternatively you can opt for storing enum values as strings. See the documentation for more details.

ObjectDB Support
✂
edit
delete

Reply

To post on this website please sign in.

ObjectDB Database Getting Started Support
DBMS Features Quick Tour with JPA ObjectDB FAQ
Editions and Prices JPA Console Tutorial ObjectDB Manual
Licence Web App Tutorial Forum
Attributions Java EE JPA Tutorial Issue Tracking
Privacy Spring MVC JPA Tutorial Website Search
Terms of Use Download ObjectDB Contact Us

Which JPA is Faster?

 

See a comparison of Hibernate, EclipseLink, OpenJPA, DataNucleus, MySQL, PostgreSQL, Derby, HSQLDB, DB4O by Versant, H2 Database, SQLite and ObjectDB

in the JPA Benchmark.

Copyright © 2003, 2010, 2024  ObjectDB Software, all rights reserved. The JPA API Reference Documentation (JavaDoc) on this website is derived with some adjustments from the open source JPA 2 RI (EclipseLink) and is available under the terms of the Eclipse Public License, v. 1.0 and Eclipse Distribution License, v. 1.0. The JDO API Reference Documentation (JavaDoc) on this website is derived with some adjustments from the JDO 2.2 API and is available under the terms of the Apache License, v. 2.0. Images on this website are available under these licecnes. Documentation on this website explains how to use JPA in the context of the ObjectDB Object Database but mostly relevant also for ORM JPA implementations, such as Hibernate (and HQL), EclipseLink, TopLink, OpenJPA and DataNucleus. ObjectDB is not an ORM JPA implementation but an Object Database (ODBMS) for Java with built in JPA 2 support.