{"id":16312,"date":"2014-02-05T19:38:38","date_gmt":"2014-02-06T01:38:38","guid":{"rendered":"http:\/\/blog.cpanel.net\/?p=16312"},"modified":"2014-02-05T19:38:38","modified_gmt":"2014-02-06T01:38:38","slug":"update-to-recent-database-prefixing-post","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/update-to-recent-database-prefixing-post\/","title":{"rendered":"Update to Recent Database Prefixing Post"},"content":{"rendered":"
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.<\/p>\n
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.<\/p>\n
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).<\/p>\n Optional Feature – Database & User Pre-Transfer Name Conflict Resolution Interface<\/strong><\/p>\n Currently, the system appends a number to the database name (for example, database2, database3, etc.) to resolve the conflict.\u00a0This is a non-interactive process, and the only indication of a conflict will appear in the transfer log.<\/p>\n 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.<\/p>\n 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.\u00a0If 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).<\/p>\n 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.<\/p>\n","protected":false},"excerpt":{"rendered":" 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 […]<\/p>\n","protected":false},"author":77,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[49],"tags":[845,45],"class_list":["post-16312","post","type-post","status-publish","format-standard","hentry","category-products","tag-11-44","tag-proddevsec"],"acf":[],"yoast_head":"\n
\nMinimum Requirements Expansion<\/strong><\/p>\n\n
\n
\n