 92 | to any numeric type. In this context numeric types are: byte, short, char, int, long, float, double, Byte, Short, Character, Integer, Long, Float, Double, BigInteger, BigDecimal and enum values ... long as the elements are convertible (e.g. from int[] to ArrayList<Long>). From any object to any |
82 | : boolean, byte, short, char, int, long, float and double. Equivalent wrapper classes from package java.lang: Boolean, Byte, Short, Character, Integer, Long, Float and Double. java.math.BigInteger ... ) collection and map types are supported, as long as their values (i.e. elements in collections and arrays |
34 | Hi, I have an object I am trying to persist (java) - It has several fields of type long[][]. It is taking very long to persist and sometimes never finish - it hangs on getTransaction().commit ... static final long serialVersionUID = 1L;
public @Id String id;
@OneToMany(fetch |
31 | key cannot be modified. It represents the entity object as long as it exists in the database. As ... 64 bit number (long) that is set automatically by ObjectDB for every new entity object that is stored ... key field:
@Entity
public class Project {
@Id @GeneratedValue long id; // still set |
30 | .**.Datapoint,com.**.Advalm);
long t0 = System.currentTimeMillis();
projects = service ... , generator = "PROJECT_SEQUENCE")
private Long id;
..
..
@OneToMany(cascade |
30 | Hi, I need to change field type in our model from long to String. After changing filed type in our model and repairing database with doctor, most of our entities is gone. Doctor puts some errors ... ? Changing a field from long to String should not require any specific action. Actually such schema |
29 | EntityManager.refresh takes a long time for entity object Person in this code:
logger.log(Level.INFO, "begin select for person " + new Date().toString());
TypedQuery personQuery =
em.createQuery("SELECT m FROM Person m", Person.class);
List |
29 | Hi! I have seen a strange behavior of ObjectDB Explorer: it shows @Id as being Long, not Integer as it's normally declared in the java class. This happens now with all entities in all 3 databases used for one project. If I open one of the entities in the explorer, then I click on it's id (in |
29 | " /> Could you explain the long time for first persist? Some operations are only required for a new |
29 | ID attribute - including inherited:
SingularAttributeLong> id1 = entityType.getId(Long ... ,Long> id2 =
entityType.getDeclaredId(Long.class);
// Checks if the type has a version ... - excluding inherited:
SingularAttributeLong> v1 = entityType.getVersion(Long.class |