Just a heads up peeps…<\/p>\n
With version 11.25.1, cPanel introduces the Database Mapping feature. This
\nfeature lays the groundwork for providing more flexibility in naming databases
\nand database users.<\/p>\n
In the past, cPanel has always appended an account’s username to any
\ndatabase name or database username created by the account (for example, a
\ndatabase might be named “user_dbname”). This changes with the
\naddition of the Database Mapping feature.<\/p>\n
In cPanel 11.25.1, Database Mapping provides the following benefits:<\/p>\n
2. Server owners can disable use of the database name prefix server-wide. If a
\nserver owner chooses this option, databases and database users will no longer
\nbe created with the cPanel account as a prefix (for example, a database could
\nbe named “dbase” instead of “user_dbase”). This option is
\nnot reversible.\n<\/ul>\n
Both the above features will make a server incompatible with older versions of
\ncPanel. If either <\/p>\n
1) a non-cPanel account is transferred to an 11.25.1 server or
\n2) the server owner opts to disable prefixing, then that server will not be
\nable to later downgrade to 11.25.0.\n<\/ol>\n
Likewise, transferring an account from a cPanel system that does not use the
\ndatabase prefix to one that does (e.g., cPanel 11.25.1 with prefixing
\ndisabled, to cPanel 11.25.0) will result in support issues. Databases and
\ndatabase users whose names lack the prefix will not be manageable in the
\ncPanel interface.<\/p>\n
Further information about Database Mapping will be published in the coming
\nweeks. <\/p>\n","protected":false},"excerpt":{"rendered":"
Just a heads up peeps… With version 11.25.1, cPanel introduces the Database Mapping feature. This feature lays the groundwork for providing more flexibility in naming databases and database users. In the past, cPanel has always appended an account’s username to any database name or database username created by the account (for example, a database might… <\/p>\n