Quote:
Originally Posted by eschwartz
The temporary folders issue (when deleting a book) only happened on unusual filesystem mounts, like when I reported this using a school computer.
It is a fat client running LTSP, so the filesystem is I believe mounted from the server computer. And it only kicked in after the book gets deleted, which if I understand correctly should be after the copy was made. Something to do with the new database backend having a new method of sending files to the trash.
|
I had them on a standard windows/ntfs rig, on a fixed internal drive. I also had a problem with hundreds of them turning up in the recycle bin
Both problems were repeatable but neither caused any loss of data or library corruption - Check Library saw them as extra author folders - but I first noticed them in my backup logs.
Both problems were fixed
Quote:
Originally Posted by eschwartz
The filename truncation was an issue involving a lack of proper support for long filenames (a Windows problem) and it meant that people expected to find their books under the usual {author}\{title} - {author}.{format} location, but didn't, since the unusually long field was given to the filesystem in shortened form. calibre kept perfect track of it, it just didn't play nice with people "looking under calibre's skirt" due to a Windows limitation.
As far as I am aware, neither should cause any problems with the books disappearing.
|
I have a vague memory that the file name truncation length changed from from 36 to 34 or something like that - it seemed to disturb a few people - although I can't recall whether they were of a material or aesthetic kind.
I can't recall them leading to disappearing books either - but there's a first time for everything.
I don't have any formal reconciliation audit controls on my libraries so a 'book' or three could easily disappear from the two larger ones without me noticing.
BR