2. Final Report Tasniflagich

3.4.2 Database schema
A database schema defines how data is organized within a relational database; this is
inclusive of logical constraints such as table names, fields, data types, and the relationships
between these entities. Schemas commonly use visual representations to communicate the
architecture of the database, becoming the foundation for an organization’s data management
discipline. Tasniflagich core features consist of 4 tables which are logically connected between.
Figure 11 shows this table structure.
Figure 11. Tasniflagich core tables
TTPU
18
2022

---

As we can see there are 4 tables:
1.
categories
1.1.
id - id of category
1.2.
version - counter of modification current record
1.3.
code - code of category
1.4.
parent_id - id of parent category
1.5.
created_at - date and time of creation record
1.6.
updated_at - date and time of last modification
1.7.
state - can be A or P (Active and Passive)
1.8.
uid - universally unique identifier
1.9.
deleted_at - null or date when record deleted
2.
products
2.1.
id - id of product
2.2.
version - counter of modification current record
2.3.
unit_id - unit_id of product
2.4.
code - code of product
2.5.
category_id - id of category
2.6.
created_at - date and time of creation record
2.7.
updated_at - date and time of last modification
2.8.
type - can be 1,2,3 (1- product, 2- work, 3- service)
2.9.
state - can be A or P (Active and Passive)
2.10.
uid - universally unique identifier
2.11.
expense_id - id of expense in table expenses
2.12.
deleted_at - null or date when record deleted
2.13.
root_category_id - id of category with second depth
3.
fields
3.1.
id - id of field
3.2.
product_id - id of product
3.3.
inputType - type of input in frontend
3.4.
isRequired - true if field is required
3.5.
created_at - date and time of creation record
3.6.
updated_at - date and time of last modification
3.7.
state - can be A or P (Active and Passive)
3.8.
uid - universally unique identifier
3.9.
index - index of field in relation of product
3.10.
unit_id - unit_id of field
3.11.
deleted_at -null or date when record deleted
4.
field_values
4.1.
id - id of value
4.2.
uid - universally unique identifier
4.3.
field_id - id of field
4.4.
state - can be A or P (Active and Passive)
4.5.
created_at - date and time of creation record
4.6.
updated_at - date and time of last modification
4.7.
index - index of value in relation of field
4.8.
deleted_at -null or date when record deleted
TTPU
19
2022

---