Deleting custom columns without opening Calibre

[Tanjamuse]

Hi.

Can I delete a custom column without having calibre open?

And how do I do that?

My Calibre is now frozen everytime I try to open the program

This is my debug log:

calibre 2.7 isfrozen: True is64bit: False
Windows-7-6.1.7601-SP1 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '7', '6.1.7601')
Python 2.7.8
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Successfully initialized third party plugins: EpubMerge && FanFictionDownLoader && Find Duplicates && User Category && Manage Series && Modify ePub && Generate Cover && Read MP3 AudioBook metadata && Count Pages && Wiki Reader && Reading List
Starting up...
QObject::killTimers: timers cannot be stopped from another thread
^C

[kovidgoyal]

start calibre like this

calibre --ignore-plugins

If that works, you know the problem is caused by some third party calibre plugin

[Tanjamuse]

How do I do that? I tried writing that in the line in my start menu, but it's still frozen.

[kovidgoyal]

Open a command prompt and type that in and press enter

[Tanjamuse]

Same result sadly. Command prompt also run as administrator.

[kovidgoyal]

Then the remaining thing to try are starting with a different library and a different config directory.

Use

calibre --with-library "c:\path\to\some\empty\folder"

and for no config

CALIBRE_CONFIG_DIRECTORY=c:\path\to\some\empty\fol der calibre

[Tanjamuse]

Opened a new calibre session with the first command.
The second gives an error.
Is this a reg-edit command?

[kovidgoyal]

Then the problem is in your library. Attach the metadata.db file from your calibre library folder.

[Tanjamuse]

I think the Metadata.db is too big to upload, it's 60 mb's.


Here's is a dropbox link instead:

https://www.dropbox.com/s/zcv107ct3i...tadata.db?dl=0

[Tanjamuse]

I have several other libraries, but that's the only one that causes Calibre to crash.

[chaley]

@Kovid: this library pushes at least three boundaries. The first is the number of books, 27,100. This isn't an excessive number of books, but it exacerbates problems 2 and 3. The second is that it contains composite columns that use composite columns, perhaps 3 and 4 deep. The third is that it uses the virtual_libraries() function and contains 40 virtual libraries, overflowing the LRU cache.

After some analysis I found that if we use get_proxy_metadata() in categories.py (line 143) instead of get_metadata(), if we up the search LRU cache up to 100 (could be less but more than 40), and if we streamline the search cache path in search._do_search then the library opens in 60 seconds on my machine. Without those changes it didn't open in the 5 minutes I waited before I ran out of patience. All of the changes were necessary to make the performance acceptable.

I have pushed a branch "perf_test" with the changes I made and made a pull request. This isn't a "real" pull request, but is instead showing what I did. I will abandon that branch once you decide what to do, if anything.

[kovidgoyal]

@chaley: I'll take a look at it in a bit, I am currently in the middle of something I would like ot finish first.

@Tanjamuse: I suggest deleting a few of your composite columns, especially the one that uses the virtual_libraries function, as they are performance killers. You should be able to do that from the command prompt like this

calibredb remove_custom_column columnname --with-library "c:\path\to\the\problem\library\folder"

Replace columnname above with the name of the column you are deleting, you can get a list of names, like this

calibredb custom_columns

[Tanjamuse]

Thanks for all the help. I got my library running again without having to deleting it all

Thanks

[Tanjamuse]

I now get an memory error every time I try to go from one library to another. Is it my computer or the program?

[chaley]

Originally Posted by Tanjamuse

I now get an memory error every time I try to go from one library to another. Is it my computer or the program?

Post the complete error message, including the traceback.