MobileRead Forums - View Single Post

tlfamm · 04-03-2014, 07:16 PM

Wanting to see what error indications might be given, I issued the following command in Windows 7:

"calibredb check_library --library-path=c:\users\Tom\L1\L2\FooLib --csv >.\CalibreChkDB.txt"

where 'FooLib' was a non-existent directory (folder) - the rest of the path was valid.

calibredb proceeded to create the missing directory, and populate it with a metadata.db file. I deleted that file, reran the above syntax, and calibredb dutifully provided another metadata.db. In both cases a null csv file resulted (signifying 'no errors' I presume).

So, if I unintentionally mistype the library name in a path specification, I receive no warning ("no such library"), but instead have an unasked-for library created?

04-03-2014, 07:16 PM	#1
tlfamm Junior Member Posts: 7 Karma: 10 Join Date: Mar 2014 Device: none	Unexpected behavior from check_library Wanting to see what error indications might be given, I issued the following command in Windows 7: "calibredb check_library --library-path=c:\users\Tom\L1\L2\FooLib --csv >.\CalibreChkDB.txt" where 'FooLib' was a non-existent directory (folder) - the rest of the path was valid. calibredb proceeded to create the missing directory, and populate it with a metadata.db file. I deleted that file, reran the above syntax, and calibredb dutifully provided another metadata.db. In both cases a null csv file resulted (signifying 'no errors' I presume). So, if I unintentionally mistype the library name in a path specification, I receive no warning ("no such library"), but instead have an unasked-for library created?