Calibre 1.48 and 2.x on the same library?

[fidvo]

I know I've asked this before when I was switching over from Windows to Linux, but I want to make sure it hasn't changed since then. Can you run Calibre 1.48 and 2.x on the same library?

Here's the context:

My laptop runs Windows XP, so I can only run 1.48. I have several other computers capable of running the newer Calibre. At the moment, I run Calibre Portable 1.48 on an external hard drive, but I would like to upgrade to the newest version to make use of some of the more recent features.

Specifically, a while back I posted an idea on the Plugin Requests thread that I would like to see in Calibre. Then Kovid happily added the feature to the next version, but since I'm still stuck on 1.48, that ironically made the feature available to everyone but the guy who requested it.

But I digress. I just came up with the idea of upgrading my portable Calibre to the latest version, and running the installed version 1.48 on my laptop, pointed to the same libraries on the external hard drive. Yes, I understand I have to use the same drive letter for my external hard drive each time.

Is there any reason this won't work?

[theducks]

Yes, it works

The only exceptions are not all user plugins are updated and some device drivers only exist in newer versions

It might care if using Calibre companion (wireless connection) reading status feature

[fidvo]

Originally Posted by theducks

Yes, it works

The only exceptions are not all user plugins are updated and some device drivers only exist in newer versions

It might care if using Calibre companion (wireless connection) reading status feature

Thanks! That's good news.

I'm aware of the limitations in 1.48 (I've been using it since it came out, after all), and I can live with them on my laptop. Likely I won't be using my laptop to do anything in Calibre except read. I might rarely update tags or other metadata manually, but I probably won't be adding or deleting books, or connecting to devices. I can do all that from my desktop, which will be running the newer Calibre.

[eschwartz]

I can't think of any backwards-incompatible changes in the database schema, which would be the only thing likely to break.

Obviously, as theducks said, some plugins are incompatible with older versions of calibre and obviously some features won't be available.
Solution -- wait until you get to the other machine to use those.


tl;dr
Should be totally safe.

[theducks]

Originally Posted by eschwartz

I can't think of any backwards-incompatible changes in the database schema, which would be the only thing likely to break.

Obviously, as theducks said, some plugins are incompatible with older versions of calibre and obviously some features won't be available.
Solution -- wait until you get to the other machine to use those.


tl;dr
Should be totally safe.

Aren't some PI still not compatible with the NEW (QT5 based) Calibre?
<obviously, the ones I use .... Are Thanks to the folk here who stepped up to the task when the originators couldn't spare time )

[eschwartz]

Originally Posted by theducks

Aren't some PI still not compatible with the NEW (QT5 based) Calibre?
<obviously, the ones I use .... Are Thanks to the folk here who stepped up to the task when the originators couldn't spare time )

http://plugins.calibre-ebook.com/porting.html

FanFicFare definitely works.
OPML Importer is incorporated in calibre IIRC.
APNX Generator is obsolete now calibre can create them during send-to-device.


The few that aren't compatible died because lack of interest.

[fidvo]

Originally Posted by theducks

Aren't some PI still not compatible with the NEW (QT5 based) Calibre?
<obviously, the ones I use .... Are Thanks to the folk here who stepped up to the task when the originators couldn't spare time )

Oh, NOW you tell me. After I already made the switch.

Just kidding.

Actually, I discovered one minor problem with plugins after updating. When switching libraries, I would get an error, which I tracked down to the Open With plugin. (Yes, I know that feature is built into Calibre now, but I'm still using the plugin until I set up all my file associations)

The latest version of the plugin caused the error. Fortunately, I stopped updating my plugins at the same time I stopped updating Calibre (until I went through and updated them all yesterday after updating Calibre), so I had a slightly older copy of the plugin in my backup. After replacing the new version with the old, the error went away.

Aside from that, I haven't found any other problems.