consider allowing calibredb read-only methods to run despite calibre running

Bug #1772293 reported by botmtl on 2018-05-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

Bug Description

could you consider allowing calibredb for the following methods even if "Another calibre program such as calibre-server.exe or the main calibre program is running."
- list
- show_metadata
- export (not sure if it's r.o.)
- catalog
- saved_searches
- list_categories
- search

botmtl (botmtl) wrote :

I should have added that I was attempting to list the methods that looked like they made no changes to the database and thus should be safe to call in that context.

There is no method that makes no changes to the database. Simply opening
a database can make changes to it (schema upgrades happen automatically
on database open).

 status wontfix

Changed in calibre:
status: New → Won't Fix

The more I think about it, the more my own question irritates me and the
stupider it gets. I apologize for not assuming competence. I really
didn't mean to do that, and did not realize that's what's I was doing until
I thought about it some. Contrary to what teachers tell us, there are
stupid questions... I just proved it.

On Sun, May 20, 2018 at 11:20 PM, Kovid Goyal <email address hidden>
wrote:

> There is no method that makes no changes to the database. Simply opening
> a database can make changes to it (schema upgrades happen automatically
> on database open).
>
> status wontfix
>
> ** Changed in: calibre
> Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772293
>
> Title:
> consider allowing calibredb read-only methods to run despite calibre
> running
>
> Status in calibre:
> Won't Fix
>
> Bug description:
> could you consider allowing calibredb for the following methods even if
> "Another calibre program such as calibre-server.exe or the main calibre
> program is running."
> - list
> - show_metadata
> - export (not sure if it's r.o.)
> - catalog
> - saved_searches
> - list_categories
> - search
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/calibre/+bug/1772293/+subscriptions
>

Not at all, it's a natural mistake to make. Lots of software does not do
automatic schema updates, requiring manual intervention from users for
it.

What I meant is that I didn't assume competence. Of course there are valid
reasons you blocked theses functions from working, you didn't suddenly
become lazy and decided it would be easier just to block everything (which
is not what I was thinking... at least not consciously, but it's what I
asked amounts too, reflecting back... and the reason I apologized).

On Mon, May 21, 2018 at 10:41 PM, Kovid Goyal <email address hidden>
wrote:

> Not at all, it's a natural mistake to make. Lots of software does not do
> automatic schema updates, requiring manual intervention from users for
> it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772293
>
> Title:
> consider allowing calibredb read-only methods to run despite calibre
> running
>
> Status in calibre:
> Won't Fix
>
> Bug description:
> could you consider allowing calibredb for the following methods even if
> "Another calibre program such as calibre-server.exe or the main calibre
> program is running."
> - list
> - show_metadata
> - export (not sure if it's r.o.)
> - catalog
> - saved_searches
> - list_categories
> - search
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/calibre/+bug/1772293/+subscriptions
>

Dont worry, part of writing open source software is developing a thick
 sin, it did not even occur to me you were being insulting. But the
 apology is appreciated nonetheless :)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers