• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

SQL Problem

C

cosmick

Guest
Say user one tried to create a database naked phpnuke

then client 2 totally differnt account tries to creat a databse called phpnuke, the system blow errors stating that database already exists. This is a problem because they are2 totally different accounts and this should not be happening because peopel do use the same names for thigns. Can someone shed some insisght on ow to fix this. Thanks
 
Heh... There are two different accouns ;)
BUT ONE MYSQL SERVER ;))
And as sequence it prevents to create two databases with the same names.
 
I see

Ok then then what do others do meaning. You know when you install phpnuke it always has a defualt database name and a lot of people just stick with that. So if I have serveral customers trying it for the first time I dont want to have to advise them to change the defualt databse name. I know I didnt my first time running nuke. So how does everyone else do it. I mean even if there were 2 SQL servers that still wouldnt be enough. So what are my options.
 
Back
Top