← Back to team overview

mudlet-makers team mailing list archive

[Bug 1068412] [NEW] db: databases can get corrupted if a profile is re-opened during same session

 

Public bug reported:

Mudlet doesn't advise for re-opening a profile that you've closed, but
it allows it nonetheless. It would seem that this can trigger a case of
database corruption - the db: init will throw an error about a "cur" row
and a -journal file will appear:

Database_namedb.db
Database_namedb.db-journal

** Affects: mudlet
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1068412

Title:
  db: databases can get corrupted if a profile is re-opened during same
  session

Status in Mudlet the MUD client:
  New

Bug description:
  Mudlet doesn't advise for re-opening a profile that you've closed, but
  it allows it nonetheless. It would seem that this can trigger a case
  of database corruption - the db: init will throw an error about a
  "cur" row and a -journal file will appear:

  Database_namedb.db
  Database_namedb.db-journal

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1068412/+subscriptions


Follow ups

References