Database requires table name prefix
Submitted by Lincoln Phipps
Link to original bug (#137547)
Description
When you run projects on hosted services they generally give you just one database (or rather they cost per database). Into this you stick all your application database tables. Its traditional that applications are able to prefix the tables with something so that there is very little chance of a name clash.
Ideally planner should do this too. We could hardcode the prefix as "planner" but also allow the user to change this in some sort of option (e.g. command line option). That would allow test and live projects to reside within one database. Very handy (essential) for migration testing.
Rgds, Lincoln.