divad / mysqladm Goto Github PK

The database size is however available in the list of databases on the server details page.

...to suggest that you put a ticket reference in the desc.

• Users can see their DBs
• Users can change their DB passwords
• Users can view server status (performance/etc.)
• Users can see stats (db size etc.)
• Users can delete database
• Users can request a new database
• Users can link into the adminer tool
• iSolutions staff to be able to create a DB via a wizard

This will better help ops teams choosing a server to place a database on.

From the Pypi page:

IMPORTANT

The checkPassword method provided by this library is meant only for testing purposes as it does not offer any protection against possible KDC spoofing. That method should not be used in any production code.

More details can be found here: https://www.calendarserver.org/ticket/833

Reported by University of Southampton Staff:

"I’ve just tried to create some databases for some LAMP sites but the MySQL manager complained about ‘invalid characters’ in the description field.
Specifically, I was trying to use:

I’m guessing its complaining about either the : or / characters.
Is there any chance these can be permitted, or alternatively for there to be some indication of the permitted characters added to the ‘create database’ screen?"

The description field is far too strict character wise and not for good reason. A simple fix to the regex should be undertaken.

Would it be possible to add the capability to validate a Delegated User account (if its not already done)?
Would it be possible to pull a user’s full name out of LDAP to display when listing Server Delegate Permissions?

If a server doesn't have an alias (ie N/A), it would be nice for the database creation summary to include the full hostname rather than just saying N/A

It should list the count of databases somewhere.

'On the “Server Status” page, it would be more useful for the “Disk Usage” graphs to display actual sizes rather than percentages.'

Allow provisioning of secondary accounts with access to a database, with either read/write or read-only permissions

• Actually cleans up the DB
• Gets around the flash() problem