summaryrefslogtreecommitdiff
path: root/releasenotes/notes
diff options
context:
space:
mode:
authorLingxian Kong <anlin.kong@gmail.com>2020-04-17 15:14:54 +1200
committerLingxian Kong <anlin.kong@gmail.com>2020-04-23 10:18:03 +1200
commita4057b10af44e7f21243e539dd2daad2ad61657b (patch)
treee8bf82b9d92ea38a5a0a030102d28af655b5a556 /releasenotes/notes
parent8c3df10aa53ca78f764c2580dc99793af03f88b9 (diff)
downloadtrove-a4057b10af44e7f21243e539dd2daad2ad61657b.tar.gz
Added checks for deleting datastore version13.0.0.0rc113.0.0
* Hard delete the datastore_configuration_parameters table record. * Make 'datastore_version_id' nullable for 'instances' table. * Check if the datastore version is still being used before removal. Story: 2007563 Task: 39451 Change-Id: I84e4a31f14f9327cc01ff2d699167d91112e1565
Diffstat (limited to 'releasenotes/notes')
-rw-r--r--releasenotes/notes/ussuri-fix-delete-datastore-version.yaml7
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/ussuri-fix-delete-datastore-version.yaml b/releasenotes/notes/ussuri-fix-delete-datastore-version.yaml
new file mode 100644
index 00000000..3a73cadb
--- /dev/null
+++ b/releasenotes/notes/ussuri-fix-delete-datastore-version.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+ - Fixed the issue that datastore version cannot be deleted because of
+ dependency of deleted instances. Now, when instance or backup is
+ deleted, the datastore version attribute is set to NULL in database.
+ When datastore configuration parameter is deleted, the record is
+ deleted from database rather than only set 'deleted' field to 1.