Is the structure of the OBD correct?



  • The main functions of the system are filling/ editing/dating the OBD tables and searching for OBD.

    All tables other than status and scientist are, like, manuals - filled separately from Scientist.

    For example, "summary_scientific_work" stores ID scientific work and relevant scientists.

    Table Education sub-tables are broken so as to prevent typographical typographical specBDEs.

    What can be simplified/improved by all NFs?

    Структура БД



  • введите сюда описание изображения

    education must be logical to make a single table with external keys on handbooks (faculty, city, name)

    The directory does not need to create 100,500 tables if there are three rows.

    as in the table of work_all, make the field under the ancestor (the truth is I don't know how academic is right, but in real life, it works at the end)

    something summarily lacks the right to life, which is a duplication and a violation of the principles of normalization.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2