Guys I am trying to make a simple ticket generation system for my company as a favor. For now, I have a table called tblTicket
and another table called tblEng
Use a column to store different logic values: check this link http://sqlpro.developpez.com/cours/stockageopt/
This means that 3 tables are necessary for data manipulation, including a significant cost to the relational query engine.
Are there way to simplify this by integrating all these data within the Member table?
Assign a code to each state:
tblTicket ( id_Ticket , Engineers )
Engineers( id_eng , other columns)
in tblTicket Engineers you can set multiple value like id_1 - id_2 - id_3 ( 1-2-3) 3 engineers
tblticket ( id_ticket , other columns ) ( primary key : id_Ticket )
engineers ( id_Eng , other columns) ( primary key : id_Eng )
TicketEng ( id_Ticket , id_Eng ) ( primary key : (id_Ticket , id_Eng) )