Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-7386

normalize the multi-value custom fields

    Details

    • Type: Improvement
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: Unscheduled
    • Fix Version/s: Unscheduled
    • Component/s: Core CiviCRM
    • Labels:
      None

      Description

      Multi Value Custom field in CiviCRM save all the values for the field in one field concatinated by chr(1).

      There are two problems with this approach.

      1.) We're not referencing to the key in the civicrm_option_value table.
      2.) it makes reporting a little hairy, especially if you are trying to attaching reporting software (ie Jasper, Business Objects) to the back-end

      The last problem is this simply isn't a normalized approach to storing data.

      I'm going to work through a roadmap on what this would take

        Attachments

          Activity

            People

            • Assignee:
              lobo Donald A. Lobo
              Reporter:
              jalama Jim Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: