I’d like to test DHIS Lite - what’s the best procedure for converting a Postgres database to H2? Is it to do a full export to DXF, switch database and then import?
···
–
Cheers,
Knut Staring
Currently, yes.
···
On Thu, Apr 2, 2009 at 9:24 AM, Knut Staring knutst@gmail.com wrote:
I’d like to test DHIS Lite - what’s the best procedure for converting a Postgres database to H2? Is it to do a full export to DXF, switch database and then import?
Note that such a DXF export and import will not transfer the html based custom forms as there is currently no support for import/export of data entry forms in the metadata export. If you need the forms you can copy and paste the html for the form directly between the databases and then use the custom form designer on the new database to relink data elements since the referenced data elements most likely have changed (the forms reference internal data element IDs).
BIRT reports also need to be copied, or simly uploaded again on the new database. Report tables will be taken of by the import/export process. The report definitions (nane of report and links to report table and birt design file) seems to be missing as well, so you might have to create them again on your new database. Is this correct Lars?
Other things not covered in the DXF import/export? geocodes for orgunits??
Ola
···
2009/4/2 Lars Helge Øverland larshelge@gmail.com
On Thu, Apr 2, 2009 at 9:24 AM, Knut Staring knutst@gmail.com wrote:
I’d like to test DHIS Lite - what’s the best procedure for converting a Postgres database to H2? Is it to do a full export to DXF, switch database and then import?
Currently, yes.
Note that such a DXF export and import will not transfer the html based custom forms as there is currently no support for import/export of data entry forms in the metadata export. If you need the forms you can copy and paste the html for the form directly between the databases and then use the custom form designer on the new database to relink data elements since the referenced data elements most likely have changed (the forms reference internal data element IDs).
BIRT reports also need to be copied, or simly uploaded again on the new database. Report tables will be taken of by the import/export process. The report definitions (nane of report and links to report table and birt design file) seems to be missing as well, so you might have to create them again on your new database. Is this correct Lars?
Yes.
Other things not covered in the DXF import/export? geocodes for orgunits??
Geocodes are included.
···
Ola
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
I guess it also should be possible to use ODBC, e.g. for the datavalues:
http://h2database.com/html/advanced.html#odbc_driver
Will take a look when I can find some time…
···
2009/4/2 Lars Helge Øverland larshelge@gmail.com
On Thu, Apr 2, 2009 at 9:24 AM, Knut Staring knutst@gmail.com wrote:
I’d like to test DHIS Lite - what’s the best procedure for converting a Postgres database to H2? Is it to do a full export to DXF, switch database and then import?
Currently, yes.