add database [entity framework core]

[allanwalpy]

Table Vacances

• id [genereted_guid:string];
• Title [string];
• Salary [salary_object:string];
• Employer [link_to_table:Organizations:many-to-one:Id];
• ContactPerson [contact.person:string];
• ContactPhone [contact.phone:string];
• EmploymentType [link_to_table:EmploymentTypes:many-to-one:Id];
• Description [string];
• LastUpdated [DateTime];

SalaryObject

subject to change: see ef core docs;

• CurrencyCode [string];
• Amount [decimal];

ContactPerson

subject to change: see ef core docs;

• Name [string];
• Soname [string];
• ThirdName [string];

ContactPhone

subject to change: see ef core docs;

• RawPhoneNumber [string];

Table Organizations

• Name[string];
• Vacancies [link_to_table:Vacancies:one-to-many];

Table EmploymentTypes

suggesting enum (populates on first database creation);

google: is it good practice store enum in database ef core or enum in database ef core;

• [string] Type;

suggestions

revisit asp.net core in action, read docs on ef core (phone numbers fields, etc.)

[allanwalpy]

hh.ru employment type:

[allanwalpy]

ef core data types

[allanwalpy]

phone validation, + mocrosoft docs

currency formatting