[xwiki-users] [XE 2.0] Live Table : not filtering multiple-valued fields
Hello, I'm using the (fantastic) new live tables to display components of a certain class. Everything works well, except for one thing - but functionality may be discutable... One of the fields of my class is of type Static List, is displayed as checkboxes and has multi-select activated. This field is correctly displayed in live table, with "type" : "list", and all checked values are displayed separated by a space character (not that good though, if some of the values contain spaces...). Problem is for sorting and filtering : - filtering on a value just leaves the table as it is (displays all entries) [Note : it seems in 2.0-RC2, filtering this kind of field removes all entries] - sorting table on this field just changes order, but with no link to values (no link I could infer). I believe sorting a multi-valued field is not really a good idea, and I wonder what to expect. As order of values is kept, it might have a sense maybe. But filtering would be helpful though. I think a line should be retained if one of the values matches the filter. Except for this case, the live table works perfectly well. WDYT ? (did not find any jira about that, maybe missed it). Regards, Jeremie
Jeremie BOUSQUET a écrit :
Hello,
I'm using the (fantastic) new live tables to display components of a certain class. Everything works well, except for one thing - but functionality may be discutable...
One of the fields of my class is of type Static List, is displayed as checkboxes and has multi-select activated. This field is correctly displayed in live table, with "type" : "list", and all checked values are displayed separated by a space character (not that good though, if some of the values contain spaces...). Problem is for sorting and filtering : - filtering on a value just leaves the table as it is (displays all entries) [Note : it seems in 2.0-RC2, filtering this kind of field removes all entries]
This would be a bug as filtering should work. I have this working on pre-2.0 livetables. Create a JIRA..
- sorting table on this field just changes order, but with no link to values (no link I could infer).
Sorting is impossible on a multi valued field. In your field definition you should say that you don't want sorting
I believe sorting a multi-valued field is not really a good idea, and I wonder what to expect. As order of values is kept, it might have a sense maybe. But filtering would be helpful though. I think a line should be retained if one of the values matches the filter.
Except for this case, the live table works perfectly well.
WDYT ? (did not find any jira about that, maybe missed it).
Regards, Jeremie _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Hello, Jira created (let you review the criticality...) : http://jira.xwiki.org/jira/browse/XWIKI-4481 By the way, I think it didn't work either in 1.9, but I would not swear it's true. Regards, Jeremie
Still not working on 2.0.3 ... By the way I noticed another bug (I think), if you agree I could create a Jira for this too. The problem is with fields of type "Database Tree". I have one, correctly displayed when showing the field with something like $doc.display(). But if I show it in a live table, and make it filterable, the combo-box that is displayed on top of the live table contains a mix of the elements of the Database Tree field, they are not ordered anymore by their relation-ships, but seem to be completely randomly displayed. And, of course, filter does not work either for this kind of field (even multiple values are not authorized for it). I tried to have a look at the queries in XWiki.LiveTableResultsMacros, but couldn't have it work after some (useless) modifications. Activated full logs, but hibernate traces are difficult to follow. It seemed that the query built by the macro page was not fetching any value, in the case of string list fields with multiple values. But on my instance, after rolling back to the initial revision, filtering magically worked for a multiple value field ! I don't know if it's a random problem, something to do with rights (don't believe so). I repeated this on my production instance, and (as expected), nothing magical occurred... Am I the only one getting this issue ? This is really diminishing the interest of live tables for me, as I have in many cases multiple-valued fields.
participants (2)
-
Jeremie BOUSQUET -
Ludovic Dubost