#1032 1.3 - Copied DB has no editable group roles

1.3
closed-wont-fix
nobody
None
5
2014-02-01
2014-02-01
Pongracz Istvan
No

I copied an existing DB to a new one.
Seems everything went fine, except there are no group roles for the DB.
The Group selection form of the User's setup also empty (of course).

The user still able to access to the DB, maybe it read these setup from the old DB/group roles?

Related

Bugs: #1032

Discussion

  • Confirmed, menu_acl contains the old setup with the old name.

     
    • Erik Huelsmann
      Erik Huelsmann
      2014-02-01

      Hi Istvan,

      That's correct. There's a (hidden) setting to work with copied databases:
      the "role_prefix" setting in the defaults table. if you put the
      "role_prefix" setting key in and have the value be
      "lsmb_<old-database-name>" (dunno about trailing underscores), that allows
      you to edit privs on the new database. But be careful - and this is why the
      setting is hidden - it will also influence whatever happens on the old
      database.

      Bye,

      Erik.

      On Sat, Feb 1, 2014 at 6:04 PM, Pongracz Istvan pongracz@users.sf.netwrote:

      Confirmed, menu_acl contains the old setup with the old name.

      Status: open
      Created: Sat Feb 01, 2014 05:01 PM UTC by Pongracz Istvan
      Last Updated: Sat Feb 01, 2014 05:01 PM UTC
      Owner: nobody

      I copied an existing DB to a new one.
      Seems everything went fine, except there are no group roles for the DB.
      The Group selection form of the User's setup also empty (of course).

      The user still able to access to the DB, maybe it read these setup from
      the old DB/group roles?


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/ledger-smb/bugs/1032/

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

      --
      Bye,

      Erik.

      http://efficito.com -- Hosted accounting and ERP.
      Robust and Flexible. No vendor lock-in.

       

      Related

      Bugs: #1032

  • Erik Huelsmann
    Erik Huelsmann
    2014-02-01

    Responded by e-mail, only to discover that the e-mail doesn't get logged in the webinterface:

    Hi Istvan,

    That's correct. There's a (hidden) setting to work with copied databases: the "role_prefix" setting in the defaults table. if you put the "role_prefix" setting key in and have the value be "lsmb_<old-database-name>" (dunno about trailing underscores), that allows you to edit privs on the new database. But be careful - and this is why the setting is hidden - it will also influence whatever happens on the old database.

    Bye,

    Erik.

     
  • Ok, so, it is by design. No problem, it is used only for testing the DB :)

     
    • status: open --> closed-wont-fix