2 | Query in JPA2 with LEFT JOIN on INNER JOIN conditions in the query WHERE clause. support Support But the result of the query is different if insert |
2 | Finding an object by its datetimeSearchBookingByTimeStamp() { Calendar btime = Calendar.getInstance(); btime.set(2012, 10, 11, 7, 30, 00); //This time is already inserted, trying to find it /* My Query */ TypedQuery<Booking> query = em.createQuery( "SELECT b FROM Booking b WHERE b.btime = :btime |
2 | wrong query result and then inserted that value again and saved the database. Repairing the database didn’t help, Attached |
2 | Unexpected exception (Error 990)I have a huge amount of inserts/updates and after a about 850.000 Entities I got the following error: [ObjectDB 2.4.7_16] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_30 (on Windows 7 6.1). Please report this error on http://www.objectdb.com/database |
2 | Field level privileges only allowed insert ability. Anonymous access only accesses some of the fields. kadirbasol Kadir BASOL |
2 | internal object DB locking in an embedded multi threaded application happen all the time but periodically. We do alot of inserts, queries and remove as we use objectdb |
2 | How best to unbind all names?My JDO application does inserts with binds, and then subsequently does bulk deletes using this code: pm.currentTransaction().begin(); Extent<ABC> extent = pm.getExtent(ABC.class, true); Query q = pm.newQuery(extent); long deletedCount = q.deletePersistentAll(); pm.currentTransaction().commit |
2 | Relationships and tracking changes @Column(name = "VERLAG_ID") @JoinColumn(name="VERLAG_ID", insertable=false, updatable=false) private |
2 | Bidirectional OneToMany is slow on updated itemsHello, I have a problem with the following situation. I insert persons with addresses. In the first run, they are all new with a new address. It runs fast. In the second run, the persons are all loaded and got a second address. This seams to be much slower. The Entities are all enhanced by |
2 | problem when primary key value is zeroI am copying data from a postgres database to objectDB. Some of the rows in the postgres table were created by postgres DDL / SQL insert statements and so do not abide by all JPA rules and recommendations, in particular there are some primary keys with value == 0. These cause problems for objectDB |
