Bug #45110
closed
File is listed twice in sys_file
Added by Philipp Gampe over 11 years ago.
Updated over 10 years ago.
Category:
File Abstraction Layer (FAL)
Description
I do not know how this can happen, but I had two different file entries for the same file in sys_file.
I create this bug report, so that we can track those kind of incidents. This could result in strange behaviors.
112 0 1359812815 1359812407 0 1 0 0 0 0 0 0 0 0 0 5 1 /templates/2013/news_v3.css css application/x-empty news_v3.css NULL da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1359815618 1359815618 0 0 NULL NULL
113 0 1359816267 1359816286 0 0 0 0 0 0 0 0 0 0 0 1 1 /templates/2013/news_v3.css txt text/x-c news_v3.css NULL dd6aa8a65e99cf98441d5c6d044fd2a5c168ee91 7552 1359816267 1359816267 0 0 NULL NULL
Is it possible that you renamed the file before, as described in #34160?
Or could it be that you deleted the file previously and re added it, so it could be #44550?
- Status changed from New to Accepted
- Target version set to 6.1.0
There is a possibility that an existing file record is not used if a file is moved. I know of this bug and we definitely have to solve it. However, I'd first like to discuss what should happen to existing records and esp. relations to them.
Imagine the following situation: Two files, identifiers /fileA and /fileB, both indexed. /fileA is now moved to /fileB, destroying the original fileB. In that case, we would have to throw away the record of fileB. This in turn would lead to dangling relations if fileB was used before.
Therefore, we have to handle this case both on the higher abstraction levels (i.e. where relations are managed) and on the low-level side (i.e. where files and their index records are managed). The latter is already there, though a bit buggy. The former has not at all been taken care of until now.
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
this is storage 0 reindexation, problems should be solved by now...
It does not happen in master for moving files any more. I suggest to close this issue and reopen the it if something like this happens again.
p.s.: I cannot close issues here.
- Status changed from Needs Feedback to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by