<\/p>\n

Core Code<\/strong>
\nDB Mapping is coded directly into cPanel. This includes modifications to our binary code base as well as the Perl Cpanel modules. We\u2019ve packed in more methods and dynamic code paths that allow cPanel to function in a forward-capable mode. We have chosen to use new models in our instantiated objects that expose new functionalities and at the same time can be rendered into the 11.25.0 user model.<\/p>\n

This new functionality is, well new, and can\u2019t always be converted to an old convention. For example, account transfers benefit tremendously from DB Mapping functionality, yet are bound to coding practicalities. Products of a new, complex code base cannot be manipulated to work in an older code base; something new can only exist in the environment for which it was designed. To put it simply, DB Mapping features are not 100% backwards compatible.<\/p>\n

DB Prefixing<\/strong>
\nPrefixing database resources is a very common practice in web hosting environments. In cPanel versions prior to 11.25.1, any database resource created by a user receives a prefix, $username_<\/em>. In 11.25.1, the DB Mapping code allows the cPanel admin to turn this prefixing requirement\/implementation off. DB Mapping decouples the textual name of the resource from the account name and stores the information separately.<\/p>\n

Mapping occurs regardless of whether Prefixing is On<\/em> or Off<\/em>. You can find the Prefix toggle in the SQL Services<\/em> section of WHM. Again, mapping is embedded in the core of cPanel which provides an easy way for cPanel admins to Opt-Out<\/em> of the Prefix paradigm. Prefixing is On<\/em> by default in 11.25.1 and the cPanel interface will continue to behave and render identical to previous versions.<\/p>\n

If you turn Prefixing Off<\/em> you cannot<\/strong> turn it back on. Additionally, you will not be able to downgrade to a cPanel version that does not have DB Mapping, e.g. 11.25.0 and below. Disabling Prefixing is a one way street.<\/p>\n