MySQL stratedgy for a customisable database

[ScrewLooseSalad]

  I've now made a php application for organising company stock, however, the company has stock stored offsite, and just acquired a new supplier that's now holding stock; as this is likely to happen again I don't want to add another column manually and add in the code myself, I need to put this ability into the app; my concern is whether allowing a php app to make columns is wise.

 

 Are there any common security risks associated with this privilege? Is there another tactic people take or am I able to add this ability in safely? Perhaps as an admin user on the app?

[mac_gyver]

your "stock" table should have a "location" column that holds the id of the location the stock is at. you should have a "location" table that you simply add a row to with a new id (auto-increment) and the new location details any time you need to add a location.