Structural Update of Database Table

Couple of days back when I was going over the database table of this site, I came across certain issues that was bothering me. I think I made some mistakes while designing the database table structure for this site. Fixing this issue is fairly easy and I can resolve this issue simply by renaming some of the tables and columns. However, renaming such tables and columns will affect the overall design of the CMS and how various records were being treated within the system The simplest response can be simply to overlook the entire issue or commit couple of hours/days to make those changes.

I honestly find it very problematic, not because I must fix those but I feel like I should. This internal struggle is also quite a daunting process for a developer. However, last night I decided to go ahead and finally start working to fix those issues.

My hosting server makes backup copy of the databases that I am currently using so grabbing a backup copy is not the issue here at all. I would have to make some internal changes to those SQL backup file which is also quite tedious. Afterwards, I can simply create a new database and simply dump those backup data to the new database.

Since this is a blog site by default, I didn't care to have any dedicated blog slug to separate the primary content on this site. However, the blog catalog has a dedicated section which has been added within the CMS as a module. In other words, I can add or remove various module within the CMS as I desire which I think was necessary feature to have.

I tried to keep this CMS as light as possible and avoid using any extra library files or framework. This makes this CMS quite easy to maintain and doesn't require whole lota work but for now, I must complete my task over the weekend.