Changes between Initial Version and Version 1 of Ticket #1129


Ignore:
Timestamp:
Oct 7, 2008, 8:24:52 PM (14 years ago)
Author:
Nicklas Nordborg
Comment:

The root problem with this is the same as for #1128. The child items are not part of the main table that builds up the table, but are fetched by additional queries (one query per column and row in the table). However, I think this problem may be easier to solve than #1128, since we don't need to retrieve the information. Possible ways forward are:

  1. Joining the tables with the child item information. I think I tried this a long time ago, but there was a problem with getting duplicate rows since we are joining a one-to-many relation.
  2. Generating subqueries that returns the id of the parent item, which is then used in the filter. Something like this this:
select * from Parent p where ... 
p.id IN (
  select p.id from Child c join c.parents p where c.name = <filter>
)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1129 – Description

    initial v1  
    1 In many cases it would be nice to be able to filter on child or parent  items in table listings. In a labeled extracts listing one would like to be able to filter on hybridizations or extracts (called 'Parents' in the view).
     1In many cases it would be nice to be able to filter on child or parent  items in table listings. In a labeled extracts listing one would like to be able to filter on hybridizations or extracts (called 'Parents' in the view).