mandatory table required by FluID loader, not present in GHO database

[Olivier Chapiteau]

the FORM_SECTION_SITE_MEMBERS table is required by the FluID loader to work, but doesn't exist in the GHO database.

- is this a missing table in GHO database ?
- is a modification needed on the loader to make this table optional ?

For now, we commented some related code in the OH loader to work :

FormSectionDimensionMembers fsdmDao = new FormSectionDimensionMembers(
                scx);
        // LinkedList fsdm = fsdmDao.findByDynamicWhere("FORM_SECTION_ID="
        // + fs.getId() + " and EFFECTIVE_DATE<=curdate() and "
        // + "(END_DATE is null or curdate()<END_DATE) "
        // + "order by DISPLAY_SEQUENCE");

        LinkedList<?> fsdm = fsdmDao.findByDynamicWhere("FORM_SECTION_ID ="
                + fs.getId() + " AND MEASURE_DIMENSION_MEMBER_ID IN "
                + "(SELECT ID " + "FROM MEASURE_DIMENSION_MEMBERS "
                + "WHERE MEASURE_DIMENSION_TYPE_ID IN " + "(SELECT ID "
                + "FROM MEASURE_DIMENSION_TYPES "
                + "WHERE TYPE_CODE = 'AGEGROUP')"
                + " AND EFFECTIVE_DATE <= NOW() "
                + " AND IFNULL(END_DATE,NOW()) >= NOW()" + ") AND ID IN "
                + "(SELECT FORM_SECTION_DIMENSION_MEMBER_ID "
                + " FROM FORM_SECTION_SITE_MEMBERS "
                + " WHERE PROJECT_SITE_ID = " + projectSiteIdNum
                + " AND EFFECTIVE_DATE <= NOW() "
                + " AND IFNULL(END_DATE,NOW()) >= NOW()" + ") "
                + " AND EFFECTIVE_DATE <= NOW() "
                + " AND IFNULL(END_DATE,NOW()) >= NOW() "
                + " ORDER BY DISPLAY_SEQUENCE ");

 HashMap<String,FormSectionSiteMember> fssm = resolveFormSectionDimensionMembersNames(
                            dtodao().scx(),
                            projectSiteIdNum);
                    fs.setFormSectionSiteMembers(fssm);

[Jiri Dvorak (jiri-dvorak)]

As per earlier e-mail conversation, we have decided that we'll keep the database schemas identicat between FluID and GHO, to allow for common OH services. Based on that decision, the table FORM_SECTION_SITE_MEMBERS and its foreign keys need to be added to the GHO schema (and any other differences between FLUID and GHO schemas need to be reconciled).

The FLUID schema WHO_GIM_FLUID_20090924.sql is attached to this item, but to be on the safe side, it is best to create an SQL schema report (e.g. via the Navicat tool) from both schemas and run "diff" on them,