MySQL is just a database. It just responds to SQL. It doesn't distinguish the contexts of such requests. As long as the user is authorised to use the database objects then as many systems can be running on the same database as you like.
Oops... typo there... Two completely separate apps. For example... I use pmachine as a content managaement system on my personal website. It uses mySQL.
I would also like to run another app that requires mySQL from my personal site, 3eprofiler (It's a character sheet app for roleplaying games). However, my host only allows one mySQL dbase per account.
I was thinking that I could just create new tables on my existing mySQL database and as long as I use a fairly strict naming convention to separate the two apps, I wouldn't run into any problems with running more than one app from the same database.
It is indeed possible to run multiple apps from the same mySQL database. You just have to be careful with the naming convention that you use for each apps tables.
For example, app1 is called pmachine so all the tables associated with that app are named something like... pm_table1.
App2 is called 3eProfiler so all the tables associated with that app are named something like... 3ep_table1.
Meaning that I will add a prefix to each table name to denote which app it belongs to. Woohoo!!! I don't have to switch hosts. Yay me!
That naming convention is just a suggestion. As I said earlier, there is no such thing as an application as far as MySQL is concerned. That's a construct of your imagination. MySQL only recognises SQL and users. What they're up to is a philosophical not technical issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.