-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
5.1
-
2
-
Severity 2 - Major
-
Currently the XML backup of active objects data stores the data based on the physical schema specific to the database from which is was exported. This means that the import of the data into a different database which supports different data types could result in a type conflict.
For example:
Postgres supports the boolean type but Oracle does not. If we attempt to write a null value to the Oracle database and specify it as type boolean, an error will be thrown.
To avoid this the data should be first converted into logical types before being stored in the XML file. This will mean it will be possible to convert the data types back to the appropriate physical type depending on the destination database.
This issue has led to previous bug:
https://jira.atlassian.com/browse/CONF-28272
- causes
-
-
- Closed
-
-
AO-419 Import of database with type boolean into a database which doesn't support boolean throws SQL exception
- Done
[CONFSERVER-28741] Import/Export of ActiveObjects plugin data should store data as logical types instead of physical types
We need something like the TypeManager which is available in the AO library. The TypeManager, however, can't be pulled directly from the AO project as we plan to keep the ao-plugin DB exporter independent of the ao library. This means we will need to implement a separate TypeManager class used only in the db exporter
Thank you for taking the time to raise, comment or vote on this Bug. Currently this bug indicates that it only impacts a version of Confluence which is no longer in support, therefore we are closing this issue as Timed Out.
If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.
Thanks again.
Regards,
Confluence Development