cPanel® Blog

Update to Recent Database Prefixing Post

First, we would like to thank everyone who has provided us with feedback on our recent blog post about database name length restrictions and database prefixing.

In response to the conversations that we have had, both online and offline, we have developed a new set of minimum delivery requirements for database users and names in cPanel & WHM version 11.44.


Minimum Requirements Expansion

  1. The setting to enforce prefixing restrictions on NEW database users and database names will be preserved. This setting will be converted from an interface in WHM (Home >> SQL Services >> Disable Database Prefix) to a tweak setting that can be enabled or disabled, and it will continue to be enabled by default.
  2. We will extend the maximum system account username length from 8 to 16 characters. However, the first 8 characters must be unique for NEW accounts in order to avoid prefix conflicts.
  3. We will allow database names and usernames to be transferred from remote systems that are NOT prefixed. We will ignore prefixing restrictions so changing users and database names will be unnecessary. This allows you to avoid changes to users’ applications.
  4. If there is a conflict between database usernames or database names during a transfer, the express transfer feature will automatically be disabled for that account (if it was requested).

These improvements to the restricted restore and transfer system are expected to increase delivery time by about four weeks. However, we may still be able to deliver the system with cPanel & WHM version 11.44 if we delay the next phase of our SSL improvements project (Spring 2014 release).

Optional Feature – Database & User Pre-Transfer Name Conflict Resolution Interface

Currently, the system appends a number to the database name (for example, database2, database3, etc.) to resolve the conflict. This is a non-interactive process, and the only indication of a conflict will appear in the transfer log.

In order to improve the visibility of this type of conflict, we could develop a new system that would allow administrators to specify new database usernames and database names when a pre-transfer conflict is detected.

  • This system would download the database usernames and database names from the remote system before the transfer begins.
  • A list of conflicting usernames and databases will display. The administrator will have the option to choose a new database name and username.

These requirements for the restricted and transfer system are expected to increase the delivery time by approximately four weeks, in addition to the minimum requirements previously listed. If these are required in order to ship the new system, then we expect the system to ship with cPanel & WHM version 11.46. Also, this would push some of the features that are already scheduled to be included in cPanel & WHM version 11.46 (Fall 2014 release) back to cPanel & WHM version 11.48 (Winter Q1 2015 release).


Please let us know if this new plan better balances your needs, and if you feel we need to include the name conflict resolution interface at the expense of delaying other features. It is our goal to offer a smoother transfer process while keeping system administration as easy as possible.

cpanellaurence

I write things. Sometimes, I edit things. Then, I publish things.