obiba / opal

OBiBa’s core database application for biobanks or epidemiological studies.
http://www.obiba.org/pages/products/opal/
GNU General Public License v3.0
29 stars 22 forks source link

OPAL-263: value missing in worksheet 'categories' when exporting from a JPA datasource to a JDBC datasource #2267

Closed ymarcon closed 6 years ago

ymarcon commented 14 years ago

Jira issue originally created by user :

==> Action: copy tables from JPA datasource to JDBC datasource, export same tables from JPA and JDBC to two excel files respectively, and then compare two excel files.

==> Step:

1) create 2 blank databases for opal application (opaldb and opal_key) and 1 blank jdbc database (opaljdbc) 2) configure 1 JPA datasources and 1 JDBC datasource in opal-config.xml: opal-data-ohs (JPA) jdbc (JDBC, mapping to opal_jdbc db) 3) import zip files exported from onyx ohs cohort to datasource 'opal-data-ohs' adm@opal>import -u ohs-unit -d opal-data-ohs 4) export N tables in 'opal-data-ohs' datasource to 'jdbc' datasource (N=7 in my test) adm@opal>copy -d jdbc opal-data-ohs.tbl1 opal-data-ohs.tbl_2 .... opal-data-ohs.tblN 5) export same tables from both datasources to excel files, one excel file for one datasource adm@opal>copy -o opal-data-ohsexport.xlsx opal-data-ohs.tbl_1 opal-data-ohs.tbl_2 .... opal-data-ohs.tblN adm@opal>copy -o jdbcexport.xlsx jdbc.tbl_1 jdbc.tbl_2 .... jdbc.tblN 6) compare worksheets with same name among 3 excel files

==> Result:

after step 6, we got 2 excel files: (see attachments) opal-data-ohs_export.xlsx (exported from opal-data-ohs datasource) jdbc_export.xlsx (exported from jdbc datasource)

compared to excel files, it's found that values missing in worksheet 'categories' in jdbc_export.xlsx.

ymarcon commented 14 years ago

Comment created by @plaflamme:

Was the JDBC Datasource configured to use a metadata table? If not, then the variables' metadata (which includes categories) was not copied to the JDBC datasource. So when you copy from the JDBC datasource to something else (say Excel) you won't have any metadata.

This is consistent with the fact that the Hips.RESFIRST_HIPSSIZE vatiable is also missing the value for "Units".

Please close issue when you've confirmed that your JDBC datasource was not configured to use a metadata table.

ymarcon commented 14 years ago

Comment created by cliu:

it worked after add following line in opal-config.xml:

      <useMetadataTables>true</useMetadataTables>
ymarcon commented 14 years ago

Issue was closed with resolution "Fixed"