Good point about the missing index on the path column.
The first thing I'd try is adding a unique index to the 'path' column as each path should be unique as they all end with the id of the artefact itself and that is unique.
The purpose of the 'path' column (if I remember right) is to handle the hierarchy issue where the child items are older (lower id) than the parent items. Eg if some files are uploaded then some folders are made and the files are moved into the folders we could end up with paths like
2/5/192/16
2/5/192/412
2/5/193/6
2/5/193/77
which were complicated to sort correctly with just the 'id' and 'parent' columns
It might make sense to have a 'artefact_path_structure' table to handle things instead of the 'path' column in the future.
Hi Brian,
Good point about the missing index on the path column.
The first thing I'd try is adding a unique index to the 'path' column as each path should be unique as they all end with the id of the artefact itself and that is unique.
The purpose of the 'path' column (if I remember right) is to handle the hierarchy issue where the child items are older (lower id) than the parent items. Eg if some files are uploaded then some folders are made and the files are moved into the folders we could end up with paths like
2/5/192/16
2/5/192/412
2/5/193/6
2/5/193/77
which were complicated to sort correctly with just the 'id' and 'parent' columns
It might make sense to have a 'artefact_ path_structure' table to handle things instead of the 'path' column in the future.
Cheers
Robert