Details
-
Bug
-
Resolution: Fixed
-
High
-
4.4
-
4.04
-
Description
If there is an ImportExportException during the AO restore then JIRA will fail to restore.
I considered this during the initial AO implementation and thought that preventing JIRA from completing the restoration was acceptable in the face of this failure. We should probably reevaluate that decision and see if it still makes sense.
Here's the problem: An ImportExportException gets triggered during XML restore. Maybe the AO file was corrupted. Maybe there's a bug in AO. Doesn't really matter. All that really matters is that we haven't fully populated the database with all the data the user expects to be present. So what do you do? Do you allow JIRA to startup and operate? The plugins will chug along but their data won't be in the right state. Will that corrupt all their user data beyond repair? Or will things basically "mostly work"?
But if we don't let them bring up JIRA how do we convey to the user what the problem is and how to fix it? Do we prevent them from using all of JIRA just because a plugin stumbles over a bug in ActiveObjects?
Attachments
Issue Links
- relates to
-
JRASERVER-25362 ActiveObjects cannot encode value for unsupported column type "ntext" on MS SQL Server 2008
- Closed