About auto

41-50 of 106Refresh
Forum
1

List always null

= GenerationType.AUTO)     private Long id;     @ManyToOne(targetEntity = Categoria.class)     private List ... = GenerationType.AUTO)     private Long id;     @OneToMany(targetEntity = Noticia.class, mappedBy = "categorias
Issue
1

New entity objects are duplicated on merge cascading

= GenerationType.AUTO)         private Long id;                 @OneToMany(cascade= CascadeType ... static class Chapter {         @Id         @GeneratedValue(strategy = GenerationType.AUTO
Forum
1

openejb jpa jaas module

methods use File | Settings | File Templates. // TODO Auto-generated method stub ... = GenerationType.AUTO,generator = "seq") @Index private int id; @Id private
Forum
1

Performance and memory usage of queries

.AUTO);    em.getTransaction().begin();    MyEntity myEntity = new MyEntity();    myEntity = em ... .setFlushMode(FlushModeType.AUTO);   em.getTransaction().begin();   Query q = em.createQuery("DELETE
Forum
1

Possible issue for default id generator

First all, congratulations to Objectdb team for the excellent work. Possible issue for default id generator when strategy is sequence. Error: Incomplete definition of auto value in field MyTestCase ... ), because it is not required (and irrelevant) for strategies such as AUTO. There are no strict rules in JPA
Forum
1

Replication error on slave restart

" /> auto" on-persist="false" on-commit="true" />  
Forum
1

Replication issue, Replayer failing due to NullPointerException.

serialization="false" />
Issue
1

Unexpected Query Token / Casting in Query

here.. (and we cannot add another one anyway in our code because it is all auto-generated). Second thing ... well?   Our stuff is auto generated and cannot be changed as it is now nor replaced with manual code
Forum
1

Relationships and tracking changes

= GenerationType.AUTO) private Long id; @OneToMany (fetch=FetchType.LAZY,cascade=CascadeType ... @Column(name = "ID") @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @ManyToOne
Forum
1

remove & persist in same transaction => Attempt to reuse an existing primary key value

Hello Support, in our configuration (FlushModeType.AUTO) is the execution of  em.find(Entity.class, ) much faster than an equivalent query. To optimize the Performance we define a special Entity ... .createEntityManager(); em.setFlushMode(FlushModeType.AUTO); System.out.println("create and persist