FileCache: parent is always -1, entries are duplicated

[blizzz]

I was looking at bugs #543 and #325 with Klaas and found following with most recent stable45 and a fresh and clean user:

After first login and running the filescan, we have of coure an empty file system. Thus, the file cache table for this user looks like:

select id,path,parent,name,size,mimetype,mimepart,writable from oc_fscache  where  user = 'leon';
+-----+-------------+--------+-------+------+----------------------+----------+----------+
| id  | path        | parent | name  | size | mimetype             | mimepart | writable |
+-----+-------------+--------+-------+------+----------------------+----------+----------+
| 193 | /leon/files |     -1 | files |    0 | httpd/unix-directory | httpd    |        1 |
+-----+-------------+--------+-------+------+----------------------+----------+----------+

Then I create a new folder. In the file cache table it will appear, but with -1 as parent instead of 193. Plus, the home folder is doubled:

select id,path,parent,name,size,mimetype,mimepart,writable from oc_fscache  where  user = 'leon';
+-----+-------------------+--------+-------+------+----------------------+----------+----------+
| id  | path              | parent | name  | size | mimetype             | mimepart | writable |
+-----+-------------------+--------+-------+------+----------------------+----------+----------+
| 193 | /leon/files       |     -1 | files |    0 | httpd/unix-directory | httpd    |        1 |
| 194 | /leon/files       |     -1 | files |    0 | httpd/unix-directory | httpd    |        1 |
| 195 | /leon/files/leaks |     -1 | leaks |    0 | httpd/unix-directory | httpd    |        1 |
+-----+-------------------+--------+-------+------+----------------------+----------+----------+

→ On a refresh of "Files", it appears empty.

→This also happens for existing user accounts.

→ I believe it clings together with the bug reports referenced to in the beginning.

[schiessle]

I think this was caused by my pull request yesterday. Sorry for the trouble. I now merged the fix #525 which should solve this issue. Please test it again, but it should be solved now.

[blizzz]

Yep, seems to solve it, thanks.