Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to the
commands.sql
file, primarily focusing on adding new checks and constraints to ensure data integrity in the database. The most important changes include adding a new function and trigger for checking specific conditions related totipoProductor
, modifying existing data insertion statements to match new constraints, and adding a new constraint to theCANTIDAD_OFRECIDA
table.New Functions and Triggers:
check_ProductorCg
function to ensure no active contract exists with the samesubastadora
andproductora
whentipoProductor
is 'Cg'.check_ProductorCg
to execute thecheck_ProductorCg
function before insert or update operations on theCONTRATO
table.Modifications to Existing Functions:
check_ContratoActivo
function to include a condition that checkstipoProductor
is not 'Cg' before raising an exception. [1] [2]Constraints and Data Integrity:
chk_idCatalogoProductora_equals_idContratoProductora
to theCANTIDAD_OFRECIDA
table to ensureidCatalogoProductora
matchesidContratoProductora
.Data Modifications:
CANTIDAD_OFRECIDA
andLOTE
tables to align with the new constraints and ensure data consistency. [1] [2]