New strategy for changing tables/records

[tigran90]

Good afternoon, colleagues.
if we decide that my migration(#808) solution is ok, then we need to rework the strategy for changing adding and deleting records.
All changes should be in /bin/db/migrations/XXX_name.php
I don't see the point in doing it manually in SQL or somewhere else.
In Git should have a dump database and fixes in the form of migration.
new regulations are needed

[dosubot[bot]]

Hey @tigran90! I'm Dosu, a bot here to help you with bug fixes, questions, and contributions. How can I assist you today?

The new regulations needed for the strategy of adding, changing, and deleting records using the migration mechanism introduced in GitHub pull request #808 are as follows:

1. Adding Records:

   • Increment the id by one for new entries.
   • Ensure all required fields are populated with valid data from legitimate sources like WikiData or Wikipedia.
   • Set created_at using NOW().
   • The flag field should be set to 1 by default.
   • Populate wikiDataId with the unique ID from wikiData.org.

2. Changing Records:

   • Update the necessary fields with valid data from legitimate sources.
   • Ensure the updated_at field is automatically updated.

3. Deleting Records:

   • Remove the record from the respective table.
   • Ensure that any dependent records in related tables are also handled appropriately to maintain data integrity.

These regulations apply to the following tables: regions, subregions, countries, states, and cities. Each table has specific required fields and data types that must be adhered to when making changes ^[1].

To continue talking to Dosu, mention @dosu.