Bob MacCallum wrote: > Hi, > > Just a few thoughts on making BASE2 easier to administrate: > > 1. It's all too easy to delete items as an administrator and then find that > you need to log in/impersonate the original owner to actually empty the > trash (they don't go into the admin user's trash). One convenient solution > which wouldn't require any major changes to the API would be to list the > trash status (empty or not) on the list of users page somewhere
The drawback is that checking if the trash is empty or not is a rather expensive operation. They only way to do that is to try to load all items in the trash and see if it is empty or not. > (clicking on this item could impersonate that user and go straight > to the trash list) You can also use the possibility to "Take ownership" of items. I think it is implemented on all list pages as well as on single-item pages. After that the deleted items appear in your own trash. Some time ago we had plans to allow an admin to select user in the trashcan view, but we implemented the "Take ownership" functionality instead. > 2. filter on "name" in the "All items" page would be nice (since I religiously > name everything with a experiment prefix). I guess there's some good > reason why this isn't already implemented. It is a technical issue. The way we use Hibernate in this case makes it impossible to filter on anything except the "owner" field. In Java terms it is because it not possible to cast an Ownable to a Nameable. Most items implement both interfaces, but not all. > 3. if the administrator could temporarily set the web application to read-only > (in the Administrate menu, for example), then backups could be made while > people still browsed It is not possible to set a "read-only" mode since just clicking around may cause updates to the database. For example, logging in creates a new row in the Sessions table and logging out closes the session and saves a lot of users settings to the database. > (or would mysqldump --lock-tables achieve basically the same thing?) I think the --lock-tables options seems dangerous. From the MySQL documentation. "...because LOCK TABLES causes any pending transactions to be committed implicitly". That would certainly not be good if a transaction is committed when it is only half-way done. The --single-transaction option seems like a better choice. As I understand it, it will not see changes (committed or not) that has happened after the dump was started. /Nicklas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
