XWiki Platform

Selecting "Relational Storage" without "Multiselect" for list properties causes loss of data during import or rollback

Details

  • Difficulty:
    Unknown
  • Similar issues:
    XWIKI-4825Altering the storage properties of a DBList or DBTreeList property sometimes fails to save the changes
    XWIKI-3128BaseClass add*List methods should allow specifying whether relational storage should be used
    XWIKI-1723multiselect separators are not defined for all list property types
    XWIKI-9013Multiple Select List values are not correctly indexed by Lucene
    XWIKI-8959Broken links created in livetables for DBList properties with multiselect activated
    XWIKI-851Rollback of a document with an attachment to a prior version without this attachment does not rollback the attachment
    XWIKI-1621Changing parameters of list properties fails
    XWIKI-7088OpenOffice import attachment error with filsystem storage
    XWIKI-2942Ability to select relational list property in XWQL
    XWIKI-1084ListClass does not fill in list with selected values which are not in the list of possible values

Description

This happens because ListClass#newPropertyfromXML expects <value> elements if either of the two is set, but <value> elements exist only if Multiselect is enabled.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sergiu Dumitriu added a comment -

Fixed in r33756.

Show
Sergiu Dumitriu added a comment - Fixed in r33756.
Hide
Permalink
Ludovic Dubost added a comment -

There is a control problem in the classe editor, because the use case "relational storage" AND NOT "multiselect" is not a wanted use case. This leads to an additional join which is not necessary when there is only one selection in the list.

It's good though to fix this bug, but we should also maybe add some control and warnings that "relational storage" should only be used with multiselect.

Show
Ludovic Dubost added a comment - There is a control problem in the classe editor, because the use case "relational storage" AND NOT "multiselect" is not a wanted use case. This leads to an additional join which is not necessary when there is only one selection in the list. It's good though to fix this bug, but we should also maybe add some control and warnings that "relational storage" should only be used with multiselect.

People

  • Assignee:
    Sergiu Dumitriu
    Reporter:
    Marta Girdea
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Date of First Response: