[OPENJPA-508] JPQL EXISTS clauses do not handle subclasses properly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.0.1
• Fix Version/s: 1.0.2, 1.1.0
• Assignee: Unassigned
• Reporter: Patrick Linskey
• Created: 01/Feb/08 20:45
• Updated: 09/Mar/10 18:32
• Resolved: 02/Feb/08 06:43

Description

The following code does not properly add subclass indicators to the generated SQL query:

StringRootEntity e = new StringRootEntity();
e.setName("foo");
em.persist(e);

e = new StringRootEntity();
e.setName("foo");
em.persist(e);

e = new StringRootEntity();
e.setName("bar");
em.persist(e);

em.flush();

Query q = em.createQuery("select o from StringAbstractEntity o " +
"where exists (select o2 from StringLeafEntity o2)");
List<StringAbstractEntity> list = q.getResultList();
assertEquals(0, list.size());

The assertion at the end fails; 3 results are returned, even though there are no SingleLeafEntity instances in the store.