Bug #2320
Trigger on data_disks table messes up the data_storage_locations.full_path column when you change the disk mount point.
Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
12/16/2011
Due date:
% Done:
0%
Estimated time:
Description
[Originally JIRA SAMDEV-38]
There's a trigger on the data_disks table which updates the data_storage_locations.full_path whenever you update the data_disks.mount_point column. However it doesn't work correctly:
select disk_id, location_id, dd.mount_point, dsl.full_path from data_disks dd join data_storage_locations dsl using (disk_id) where disk_id = 816; 816 1212056 /storage/gpfs_cdf8/sam/cache25 cdfsam.cnaf.infn.it:/storage/gpfs_cdf8/sam/cache25//boo update data_disks set mount_point = '/storage/gpfs_cdf0/sam/cache25' where disk_id = 816; select disk_id, location_id, dd.mount_point, dsl.full_path from data_disks dd join data_storage_locations dsl using (disk_id) where disk_id = 816; 816 1212056 /storage/gpfs_cdf0/sam/cache25 cdfsam.cnaf.infn.it:/storage/gpfs_cdf0/sam/cache25/gpfs_cdf8/sam/cache25//boo
Not exactly what I was expecting.
I think it's the complicated looking trigger 'DD_UPDATES_BEF_U' which is doing this.
History
#1 Updated by Robert Illingworth almost 8 years ago
- Priority changed from Normal to Low