#703 Revert R-O databases on lock

closed
nobody
None
5
2013-09-24
2013-03-18
No

Please add another System checkbox to set another behavior: If checked, and when a DB is opened read-only either explicitly or by default, then when it's locked, it should revert back to read-only. If we've chosen read-only by default, there's no reason to stay read-write when locked, right? Altho at that point, we probably also want the "Open as read-only" checkbox on the unlock dialog. Essentially unlocking becomes nearly identical to opening.

We do love the read-only feature! It helps this work in our environment. But someone will change to R-W to add or edit, and then forget they have. Later, often much later, someone else will want to add or edit, and we get the dreaded message that we cannot change to R-W, and have to go find someone, or kill their process. This is what we came up with for a solution.

Related

Feature Requests: #703

Discussion

  • Rony Shapiro

    Rony Shapiro - 2013-08-16

    I wouldn't add this as another checkbox, but rather make this the default behavior for changing from r-o to r/w. That is, the way the database is initially opened is 'persistent'. If the mode is changed in the course of work, that change will not persist across locks.

     
  • Rony Shapiro

    Rony Shapiro - 2013-08-25
    • status: open --> pending
     
  • Rony Shapiro

    Rony Shapiro - 2013-08-25

    Implemented per previous comment by DrK. Will be in 3.32

     
  • Greg Stigers

    Greg Stigers - 2013-09-14

    Rony,

    Wonderful! Thanks! I hope users find this useful. We think it will be.
    When will 3.32 likely be available?

    -Greg Stigers

    Quoting Rony Shapiro ronys@users.sf.net:

    Implemented per previous comment by DrK. Will be in 3.32


    [feature-requests:#703] Revert R-O databases on lock

    Status: pending
    Created: Mon Mar 18, 2013 10:46 PM UTC by Greg Stigers
    Last Updated: Fri Aug 16, 2013 04:18 PM UTC
    Owner: nobody

    Please add another System checkbox to set another behavior: If
    checked, and when a DB is opened read-only either explicitly or by
    default, then when it's locked, it should revert back to read-only.
    If we've chosen read-only by default, there's no reason to stay
    read-write when locked, right? Altho at that point, we probably also
    want the "Open as read-only" checkbox on the unlock dialog.
    Essentially unlocking becomes nearly identical to opening.

    We do love the read-only feature! It helps this work in our
    environment. But someone will change to R-W to add or edit, and then
    forget they have. Later, often much later, someone else will want
    to add or edit, and we get the dreaded message that we cannot
    change to R-W, and have to go find someone, or kill their process.
    This is what we came up with for a solution.


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/passwordsafe/feature-requests/703/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Feature Requests: #703

  • Rony Shapiro

    Rony Shapiro - 2013-09-24
    • Status: pending --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks