8 | Selective merge/cascade of detatched entityI'm having an issue with my application, and I'm hoping you guys will be able to help. Please forgive typos and obvious errors, I'm having to retype from a non-internet connected network. A contrived example is: @Entity public class Salesman { private String name; @OneToMany(fetch |
6 | ClassCastException of same object type is to eventually have the application used over a network via the server. So having |
6 | Removing objects where ManyToMany relationships exist a TreeSet automatically removed as well, so, the TreeSet is reduced in size? Or do I end up having |
6 | mapping file is not being loadedHi, I am evaluating ObjectDB by using it with an in-house developed library in order to prototype its capabilities / performance. I am having a problem in that the in-house library in question reads a simple configuration file to determine available persistence units, and then bootstraps them using |
6 | _PersistenceException: Type is not found on getSingleResult.Greetings. I'm new to ObjectDB. I'm using an ObjectDB local database for a Java SE standalone application and i'm having issues querying for an object of this entity: @Entity public class Estudiante{ @Id @GeneratedValue private Integer id; @Column private String |
6 | Problem with Criteria QuerysHi, i am having problems running following code... import java.util.*; import javax.persistence.*; import javax.persistence.criteria.CriteriaBuilder; import javax.persistence.criteria.CriteriaQuery; import javax.persistence.criteria.ParameterExpression; import javax.persistence.criteria.Root |
6 | NontransactionalWrite error using Collections.sort .Hi, i started to use ObjectDB today and i'm having problem using command Collections.sort in persisted object. Attempt to modify an object with no active transaction when NontransactionalWrite is disabled: br.ufpa.linc.MetriX.api.model.Interface#105 (error 635) I don't want to modifi de object in |
6 | Duplicate Entity class names causes Exception in Query it works without having to use qualified entity names. Sorry, I didn't see that you only want |
1 | Query fails with failed to read access mode instead of doing nothing, especially after having a c/s connection the usage before ... nothing, especially after having a c/s connection the usage before. There is a change in one of the recent |
1 | Best practice for history trackingWe would like to add to records start and end timestamp fields. When end field is null, it indicates the last version of this item. Few questions: in terms of performance, what would be faster, having a single timestamp and looking for the top1 when ordered by time or the above solution, looking |
