{"id":34734,"date":"2019-10-31T22:00:06","date_gmt":"2019-10-31T19:00:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/sravnenie-i-vybor-sistem-migratsii-dannyh\/"},"modified":"2019-10-31T22:00:06","modified_gmt":"2019-10-31T19:00:06","slug":"sravnenie-i-vybor-sistem-migratsii-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/sravnenie-i-vybor-sistem-migratsii-dannyh","title":{"rendered":"Adatmigr\u00e1ci\u00f3s rendszerek \u00f6sszehasonl\u00edt\u00e1sa \u00e9s kiv\u00e1laszt\u00e1sa","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Adatmigr\u00e1ci\u00f3s rendszerek \u00f6sszehasonl\u00edt\u00e1sa \u00e9s kiv\u00e1laszt\u00e1sa<\/h2>\n

\n\"Adatmigr\u00e1ci\u00f3s
\n
\nA model in the development process tends to change, and at some point, it no longer matches the database. Of course, the database can be deleted, and then the ORM will create a new version that corresponds to the model, but this procedure will result in the loss of existing data. Thus, the function of the migration system is to synchronize the schema with the data model in the application without losing existing data.<\/p>\n

In this article, we would like to explore various tools for managing database migrations. We hope that this overview will be useful for developers faced with such choices.
\n<\/a><\/noindex><\/p>\n

Feladat<\/h3>\n

\nOur company is currently actively developing the next generation of the product \u2013 Docs Security Suite (DSS). The server side is being written in .Net Core, and we are accordingly using Entity Framework Core as the database management system. When designing the application, we use a Code First approach.<\/p>\n

The domain model of the application is created by several developers simultaneously \u2013 each responsible for their logical part of the system. <\/p>\n

In the previous generation of DSS, classic Entity Framework Migrations (EF 6) was used as the migration management system. However, it has accumulated some complaints, the main one being that EF lacks a reasonable approach to resolving version conflicts. This fact still troubles us during bug fixing in support, which is why a decision was made to consider alternative options.<\/p>\n

As a result of the discussion, the following requirements were formed for the migration management system:<\/p>\n

    \n
  1. Support for various DBMS. MS SQL Server, PostgreSQL, Oracle are mandatory, but potentially other databases can also be used.<\/li>\n
  2. Work with ORM. Initially, EF Core was assumed for use, but during the design phase, we were open to considering other ORMs.<\/li>\n
  3. Autogeneration of migrations. Given the development of Code First, we would like to avoid the need to \"write migrations by hand\".<\/li>\n
  4. Version conflicts. In a distributed development environment, when merging, EF Core can fail due to conflicts. This becomes a significant problem since different parts of the application are created by different developers, requiring a lot of time spent on each merge.<\/li>\n
  5. Fejlett dokument\u00e1ci\u00f3 \u00e9s t\u00e1mogat\u00e1s. Itt, \u00fagy v\u00e9lj\u00fck, a magyar\u00e1zatok nem sz\u00fcks\u00e9gesek.<\/li>\n
  6. Ingyeness\u00e9g. A krit\u00e9rium felt\u00e9teles, mivel a nem t\u00fal dr\u00e1ga rendszerek vagy dr\u00e1ga, de k\u00e9nyelmes megold\u00e1sok is sz\u00f3ba j\u00f6hetnek.<\/li>\n<\/ol>\n

    \nEgy kisebb kutat\u00e1s eredm\u00e9nyek\u00e9nt a k\u00f6vetkez\u0151 lehet\u0151s\u00e9geket tal\u00e1lt\u00e1k \u00e9s ismerik el k\u00edv\u00e1natosnak a megfontol\u00e1sra:<\/p>\n

      \n
    1. EF Core Migrations<\/li>\n
    2. DBup<\/li>\n
    3. RoundhousE<\/li>\n
    4. ThinkingHome.Migrator<\/li>\n
    5. Fluent Migrator <\/li>\n<\/ol>\n

      <\/p>\n

      Most pedig egy kicsit r\u00e9szletesebben<\/h3>\n

      \n\"Adatmigr\u00e1ci\u00f3s
      \n      EntityFramework Core Migrations<\/a><\/noindex><\/b><\/p>\n

      Term\u00e9szetesen ez volt az els\u0151 \u00e9s f\u0151 v\u00e1laszt\u00e1s. Nat\u00edv eszk\u00f6z, ami dobozb\u00f3l kih\u00fazva m\u0171k\u00f6dik, mindenf\u00e9le tr\u00fckk\u00f6z\u00e9s n\u00e9lk\u00fcl. Nagy mennyis\u00e9g\u0171 dokument\u00e1ci\u00f3, hivatalos \u00e9s nem hivatalos, egyszer\u0171s\u00e9g stb. Azonban a klasszikus EF-hez feltett panaszok teljesen relev\u00e1nsak az EF Core eset\u00e9ben is. <\/p>\n

      \u00cdgy az EF Core-hoz a k\u00f6vetkez\u0151 el\u0151ny\u00f6k tartoznak:<\/p>\n