6 | JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception is now a jboss module there is no more need to include it in the lib of the .war having objectdb |
6 | Calculating age in query?Hi! I've got an issue: I have a birthdate as java.sql.Date and a separate field int age. However, of course the age is not accurate because it gets set only once. So what's the best bet (JPA Standard way) to solve the issue of accessing and filtering by an age (having a birthdate) in a query |
6 | multi thread application, id field sporadically nullWe are testing objectDB with a multi thread application. Each thread has it's own entityManager created from a common factory. In one thread we receive sometimes an object from the database with the field that is declared as @Id having the value null (what is not correct, we checked |
6 | How to move @Embedable collection to a dedicated entity class?. How should delete all children of a specific parent? Having a parent with 500K children, when I clear |
6 | Left join fetch behaviour doesn't retrieve children? was moved to a separate forum thread. xirt Sylvain Support, I have done some benchmarks ( after having |
6 | Optimization of Map Querieshi! I am having loads and loads of occurrences of something like ((com.test.MyEntity) $1.map.get('com.test.MyEntity')).someProperty ... ((com.test.MyEntity) $1.map.get('com.test.MyEntity')).someOtherProperty .. ((com.test.MyEntity) $1.map.get('com.test.MyEntity')).someMoreProperties I need |
6 | Time Sequence Object Command DB without having to update objects defined using the older schemas. When the database is loaded |
6 | Problem with bidirectional link(I had raised this issue in the past and have finally had time to come back to it and strip down the classes to a minimum). The problem seems to lie in having bidirectional links (viz, I have @OneToMany Map<String, Entry> children and @ManyToOne Entry parent in my classes. I've attached |
6 | Using aliases in WHERE clause The processing order of a query is: FROM -> WHERE -> GROUP BY -> HAVING -> SELECT -> ORDER BY Accordingly |
1 | Issue with DISTINCT Select, what is the desired, JPA-Conform way of NOT having a result with doubled $1 and stilll use |
