Quote:
Originally Posted by fidvo
To be fair, the tone of the original post in this thread was openly hostile. Is it any wonder that the responses are less than friendly?
But that's the correct answer to the question. The answer doesn't change no matter how many times the question gets asked.
I don't see it as particularly rude; it's just concise. There's no "We're sorry that the database structure doesn't conform to the way you would like to do things..." It just tells it like it is.
I'm also curious about EowynCarter's project, specifically how he addressed the issues mentioned by itimpi:
EowynCarter must have come up against these exact same issues, and found some way to deal with them. Synchronization between the database and the files is the single biggest reason why Calibre adopted a "hands-off" policy, so if EowynCarter's program finds a solution to this, I'm very interested in knowing how.
|
Well, touching the files outside the program is still no go. But it's read only i'm interested in.
I have some resync, clean database, then goes through all the folder to rebuild it.
Java have some feature to watch for filesystem changes. In my case, it's a webserver, so could probably do.
What can be done is to have the database store the date the file was last edited, so as to detect conflict.
Then you have to goes though two loops to detect stuff in database no
longer in filesystem and vice-vera.