[TAP5-1971] HibernateGridDataSource should include some workaround or protection agains wrong Projections.rowCount() result

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Incomplete
• Affects Version/s: 5.3.3
• Component/s: tapestry-hibernate
• Labels: bulk-close-candidate
• Assignee: Unassigned
• Reporter: Andrei Arapov
• Created: 09/Jul/12 08:01
• Updated: 22/Aug/16 06:47
• Resolved: 22/Aug/16 06:47

Description

In some cases Hibernate's criteria construction like "criteria.setProjection(Projections.rowCount())" returns wrong number of rows. More specifically, for example, if you have some JPA restrictions in you entity annotations (e.g.
" @ManyToOne
@JoinColumn(name = "USER_ID", nullable = false) <---- this one!
@NonVisual
public UserImpl user; ")

then such restrictions (for USER_ID is not null) will not be taken in account while building "row-count" query.

Vice-versa hibernate will use such restrictions in query for getting LIST of entities.

This behaivour fails, when in entity table appear (e.g. some old) rows with NULL in "USER_ID" (e.g.) columns.

This is known, but not solved problem for Hibernate, see:
https://hibernate.onjira.com/browse/HHH-3238
https://hibernate.onjira.com/browse/HHH-2787
https://hibernate.onjira.com/browse/HHH-3206
https://hibernate.onjira.com/browse/HHH-5719
https://hibernate.onjira.com/browse/HHH-4829
https://hibernate.onjira.com/browse/HHH-7438

There by we go into error in HibernateGridDataSource.getRowValue(int index) method: it throws IndexOutOfBoundsException due to row count number is bigger than actual number of selected rows.