Opened 16 years ago
Closed 16 years ago
#783 closed task (fixed)
Check the source for other places affected by the Postgres problem described in ticket #781
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | minor | Milestone: | BASE 2.4.3 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description (last modified by )
Since it only affects distinct queries we can use Eclipse to find all places where Query.setDistinct() is called. More info at #781.
Change History (6)
comment:1 Changed 16 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 16 years ago by
| Description: | modified (diff) |
|---|
comment:3 Changed 16 years ago by
| Milestone: | BASE 2.5 → BASE 2.4.3 |
|---|---|
| Priority: | major → minor |
comment:4 Changed 16 years ago by
| Owner: | changed from everyone to Nicklas Nordborg |
|---|---|
| Status: | new → assigned |
comment:5 Changed 16 years ago by
comment:6 Changed 16 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Can't find any more places. The problem found is now part of ticket #785.
Note: See
TracTickets for help on using
tickets.
I have found that BioMaterialEvent?.getQuery() also creates a DISTINCT query. The web interface has options to sort by protocol and owner, which doesn't work in Postgres. This case is probably more difficult to solve, since the query is built by generic code, that isn't aware of the problem.
The target method to check for a solution is ItemContext?.configureQuery() which already has an option for left joins. Maybe we can try to use a LEFT FETCH JOIN if the query is distinct.