What is the best way to organize database migrations on production in Drupal?

Question

CMS

The developer is engaged in the creation of modules, while making changes to the database (for example, creating tables or adding records). After he has finished this process and everything has been tested, it is necessary to upload the changes to production. There are no problems with the code, but here's how to upload the changes he made to the database on production, while maintaining the data that is already there? Perhaps someone has encountered such a task in Drupal and can tell you how best to organize this process?

Thanks in advance.

Answer 1

The module should create all its database changes in the .install file. You install the module on production, it adds everything you need to the database.

Answer 2

There are modules for migration based on Features, but I think they are at the alpha stage.
For Drupal, this is a tough question. Six months ago I was looking for a solution, but did not find it.
Therefore, while we are developing the module, we do not enter any data.