Author Topic: Read Only Database - Crash  (Read 693 times)


  • Jr. Member
  • **
  • Posts: 6
Read Only Database - Crash
« on: April 05, 2019, 09:43:54 PM »
Apparently PG Offline doesn't like the messages.db3 file set to "read only"?

I archived a group and didn't want the file (a bit over a terrabyte in size) corrupted. but alas, PF Offline crashes after a brief time after it lists messages (or tries to do anything, actually).

Removing the "read only" flag on the db3 file restores PG Offline to a happy state again. Not a complaint necessarily, just logging and noting behavior.

UPDATE: Under > File >Options > Misc the setting "Mark message as read after [5] sec." Apparently PGO throws a tantrum when it can't?
« Last Edit: April 05, 2019, 10:25:14 PM by Steeley »

Wilson Logan

  • Administrator
  • Hero Member
  • *****
  • Posts: 2794
    • Email
Re: Read Only Database - Crash
« Reply #1 on: April 06, 2019, 02:07:45 AM »
SQLite does its own internal housekeeping for which it requires write access.

You cannot "read" an SQLite database in read-only mode because it has to maintain for example, its lock table, last accessed date, etc, etc.




SMF spam blocked by CleanTalk