scubakevin

Registered
Oct 25, 2003
4
0
151
Cancun
Can someone help me to understand why in gods name does the CPANEL add the username_ to all of my databases and database users names???

I am trying to migrate a shitload of heavy DB's and Sites that are all database driven and I have never seen anything where when I create a DB name the stupid system adds a prefix to it preventing me from using existing config files for all of the sites that I am migrating.

I installed phpMyAdmin as a standalone in one of the sites to test and used the root user and pass for MySql and it allowed me to do everything except.........Actually use the databases and usernames created. I could not even see them in the cpanel for that site using phpmyadmin.

Anybody got any ideas to get around this or is it better to just get rid of cpanel and go back to controlling server from ssh?

Between the issues of the open ssl, mysql database, and some other stupid stuff I am really disappointed in the $1500 investment plus having a tech install it.

Some of the features are nice but I feel like I lost alot.

Hanna
 

jsteel

Well-Known Member
Jul 4, 2002
646
0
166
Atlanta, GA
Originally posted by scubakevin
Can someone help me to understand why in gods name does the CPANEL add the username_ to all of my databases and database users names???

I am trying to migrate a shitload of heavy DB's and Sites that are all database driven and I have never seen anything where when I create a DB name the stupid system adds a prefix to it preventing me from using existing config files for all of the sites that I am migrating.

I installed phpMyAdmin as a standalone in one of the sites to test and used the root user and pass for MySql and it allowed me to do everything except.........Actually use the databases and usernames created. I could not even see them in the cpanel for that site using phpmyadmin.

Anybody got any ideas to get around this or is it better to just get rid of cpanel and go back to controlling server from ssh?

Between the issues of the open ssl, mysql database, and some other stupid stuff I am really disappointed in the $1500 investment plus having a tech install it.

Some of the features are nice but I feel like I lost alot.

Hanna
For one, to guarantee uniqueness without receiving errors saying the database already exists.

For two, since mysql owns the DBs, there must be an easy way to identify who owns the databases for multiple different needs in the system (quotas, account backups, copying accounts, etc.).