I am in doubt about the database modeling I mention the case: I have a database with some of the tables that are
PERSONA (nro_documento,apellidos,nombres,fnacimiento,id_genero,id_tdocumento)
TRABAJADOR (nro_documento,codtrabajador,sueldo,id_departamento)
FORMACION (nro_documento,institucion,descripcion,id_tformacion,id_eformacion)
CONTRATO (nro_documento,id_contrato,inicio,fin,cese,remuneracion,id_tcontrato,id_econtrato)
ENTRADA_SALIDA (nro_documento,id_es,fecha,hora,id_tes,id_ees)
In addition to
GENERO (id, codigo, etiqueta, descripcion, situacion)
TIPO_DOCUMENTO
ESTADO_CIVIL
TIPO_TRABAJADOR
ESTADO_TRABAJADOR
TIPO_FORMACION
ESTADO_FORMACION
TIPO_CONTRATO
ESTADO_CONTRADO
TIPO_E_S
ESTADO_E_S
(all these last with same attributes).
Main Cardinality:
persona (1 a 1) trabajador
trabajador (1 a n) formacion
trabajador (1 a n) contrato
trabajador (1 a n) entrada_salida
The mentioned thing is the current state of the modeling, what I want to do is the tables (genre, document_type, civil_state, worker_type, worker_state, type_formation, state_formation, type_contract, state_contracted, state_e_s and type_e_s) remove them and represent them by 2 which they are entity_type and entity, where:
//representa las diferentes tablas que quitare
TIPO_ENTIDAD (cod_te,etiqueta,situacion)
//son las opciones que tienen cada una
ENTIDAD (id,codigo,etiqueta,descripcion,situacion,cod_te)
Cardinality:
TIPO_ENTIDAD (1 a n) ENTIDAD
BEFORE:
AFTER:
Is it advisable to do what I mention or not ?, I say it because if at some point I create a table informatic_computer this will have a type and status that with the current situation would create two tables in the base while with the situation that I think only one pair of records in the table type_entity.