Skip to content

Commit

Permalink
chore: cleanup commit_form_change_internal
Browse files Browse the repository at this point in the history
  • Loading branch information
@mikevespi
mikevespi committed Mar 22, 2024
1 parent 2279a95 commit 5483b43
Showing 1 changed file with 59 additions and 52 deletions.
111 changes: 59 additions & 52 deletions schema/deploy/mutations/commit_form_change_internal.sql
View file
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,10 @@ begin

if pending_project_revision_id is not null then
if fc.operation = 'create' then
/*
These are the forms that a project can have at most one of.
If pending has created one alredy, then we need to set the previous_form_change_id and the form_data_record_id.
*/
/*
These are the forms that a project can have at most one of.
If pending has created one alredy, then we need to set the previous_form_change_id and the form_data_record_id.
*/
if (
(fc.json_schema_name in ('funding_parameter_EP', 'funding_parameter_IA', 'emission_intensity', 'project_summary_report')) and
((select count(id) from cif.form_change where project_revision_id = pending_project_revision_id and json_schema_name = fc.json_schema_name) > 0)
Expand All @@ -53,12 +53,20 @@ begin
form_data_record_id = recordId
where project_revision_id = pending_project_revision_id
and json_schema_name = fc.json_schema_name;


/*
If the committing form_change is creating a project contact, and the contactIndex already exists in the pending revision,
then update the index of the pending form_change to be the highest current index + 1 to avoid the clash.
If the contactIndex does not exist in the pending proejct revision, then the catch-all case for creates handles it.
*/
elsif (
fc.json_schema_name = 'project_contact'
and (select count(id) from cif.form_change where project_revision_id=pending_project_revision_id and json_schema_name=fc.json_schema_name) > 0
and (select count(*) from cif.form_change where
project_revision_id = pending_project_revision_id and
json_schema_name = 'project_contact' and
new_form_data ->> 'contactIndex' = fc.new_form_data ->> 'contactIndex') > 0
) then
-- if pending has any contacts, then create the new form change in pending and update the contactIndex to be the highest
-- contactIndex in pending + 1. If it doesn't then the catch-all for 'create' will handle it
select id into new_fc_in_pending_id from cif.create_form_change(
operation => 'update'::cif.form_change_operation,
form_data_schema_name => 'cif',
Expand All @@ -68,23 +76,23 @@ begin
json_schema_name => fc.json_schema_name,
new_form_data => (fc.new_form_data || format('{"contactIndex": %s}',
(select max((new_form_data ->> 'contactIndex')::int) from cif.form_change
where project_revision_id=pending_project_revision_id
where project_revision_id = pending_project_revision_id
and json_schema_name = fc.json_schema_name
) + 1)::jsonb
)
);
update cif.form_change set previous_form_change_id = fc.id where id = new_fc_in_pending_id;

/*
If the projectManagerLabelId already exists in pending, set the form_data_record_id and previous_form_change_id,
and the operation to 'update' to handle when pending has an opertion of 'create'. If not, then the catch all case will handle it.
*/
/*
If the projectManagerLabelId already exists in pending, set the form_data_record_id and previous_form_change_id,
and the operation to 'update' to handle when pending has an opertion of 'create'. If not, then the catch all case will handle it.
*/
elsif (
fc.json_schema_name = 'project_manager'
and (
(select count(*) from cif.form_change
where project_revision_id=pending_project_revision_id
and json_schema_name=fc.json_schema_name
where project_revision_id = pending_project_revision_id
and json_schema_name = fc.json_schema_name
and new_form_data ->> 'projectManagerLabelId' = fc.new_form_data ->> 'projectManagerLabelId') > 0
)
) then
Expand All @@ -93,21 +101,21 @@ begin
form_data_record_id = recordId,
operation = 'update'::cif.form_change_operation
where id = (select id from cif.form_change
where project_revision_id=pending_project_revision_id
and json_schema_name=fc.json_schema_name
where project_revision_id = pending_project_revision_id
and json_schema_name = fc.json_schema_name
and new_form_data ->> 'projectManagerLabelId' = fc.new_form_data ->> 'projectManagerLabelId');

/*
If reporting_requirements of this reportType already exist in pending, create the new form_change and set the reportingRequirementIndex
to the highest existing in pending plus 1. If committing is the first reporting_requirement of this reportType, then the catch-all works.
*/
/*
If reporting_requirements of this reportType already exist in pending, create the new form_change and set the reportingRequirementIndex
to the highest existing in pending plus 1. If committing is the first reporting_requirement of this reportType, then the catch-all works.
*/
elsif (
fc.json_schema_name = 'reporting_requirement'
and (
(select count(id) from cif.form_change where project_revision_id = pending_project_revision_id
(select count(*) from cif.form_change where project_revision_id = pending_project_revision_id
and json_schema_name = fc.json_schema_name
and new_form_data ->> 'reportType' = fc.new_form_data ->> 'reportType')
> 0)
> 0)
) then
select id into new_fc_in_pending_id from cif.create_form_change(
operation => 'update'::cif.form_change_operation,
Expand All @@ -126,11 +134,11 @@ begin
);
update cif.form_change set previous_form_change_id = fc.id where id = new_fc_in_pending_id;

/*
If committing is creating a milestone and milestones exist, create the milestone in pending and set the
reportingRequirementIndex to be the max existing in pending plus 1.
If pending has no milestones, the catch-all works.
*/
/*
If committing is creating a milestone and milestones exist, create the milestone in pending and set the
reportingRequirementIndex to be the max existing in pending plus 1.
If pending has no milestones, the catch-all works.
*/
elsif (
fc.json_schema_name = 'milestone'
and (
Expand All @@ -154,12 +162,12 @@ begin
);
update cif.form_change set previous_form_change_id = fc.id where id = new_fc_in_pending_id;

/**
This next case acts as the catch-all for 'create'. It applies to any scenario in which the pending revision does not have an equivalent
form change to the one being committed. This includes unordered lists (e.g. attachments, milestones, etc.), the unique forms
like funding_parameter when pending has not created one yet, and ordered/pseudo ordered lists when the equivalent index does not
exist in pending.
**/
/**
This next case acts as the catch-all for 'create'. It applies to any scenario in which the pending revision does not have an equivalent
form change to the one being committed. This includes unordered lists (e.g. attachments, milestones, etc.), the unique forms
like funding_parameter when pending has not created one yet, and ordered/pseudo ordered lists when the equivalent index does not
exist in pending.
**/
else

select id into new_fc_in_pending_id from cif.create_form_change(
Expand Down Expand Up @@ -188,26 +196,25 @@ begin
select (cif.jsonb_minus(fc.new_form_data, parent_of_pending_form_change.new_form_data))
into committing_minus_pendings_parent;

/*
If the committing and pending form changes both have changes from the pending form change's parent,
then set the pending form change's new_form_data to be the committing form change's, and apply the changes
made in the pending form change to that data.
*/
/*
If the committing and pending form changes both have changes from the pending form change's parent,
then set the pending form change's new_form_data to be the committing form change's, and apply the changes
made in the pending form change to that data.
*/
if committing_minus_pendings_parent is not null then
if pending_minus_pendings_parent is not null then
update cif.form_change
set new_form_data =
(fc.new_form_data || pending_minus_pendings_parent)
where id = pending_form_change.id;

/*
If the pending form change hasn't made any changes since its creation, but the committing form change has,
set the pending form change's new_form_data to be the committing form_change's, as it is the latest information.
*/
/*
If the pending form change hasn't made any changes since its creation, but the committing form change has,
set the pending form change's new_form_data to be the committing form_change's, as it is the latest information.
*/
else
update cif.form_change
set new_form_data =
(fc.new_form_data)
set new_form_data = (fc.new_form_data)
where id = pending_form_change.id;
end if;
end if;
Expand All @@ -225,11 +232,11 @@ begin
select (cif.jsonb_minus(pending_form_change.new_form_data, parent_of_pending_form_change.new_form_data))
into pending_minus_pendings_parent;

/*
If pending has made changes, then set its operation to create and null the form data record id & previous form change id
since it's technically creating them now. This way the archiving still took place in the committing form change, and we
avoid trying to update the now archived record that form_data_record_id points to.
*/
/*
If pending has made changes, then set its operation to create and null the form data record id & previous form change id
since it's technically creating them now. This way the archiving still took place in the committing form change, and we
avoid trying to update the now archived record that form_data_record_id points to.
*/
if pending_minus_pendings_parent is not null then
update cif.form_change set
operation = 'create'::cif.form_change_operation,
Expand All @@ -238,9 +245,9 @@ begin
where id = pending_form_change.id;

else
/*
If pending has not made changes to the form data, the pending record can be deleted as it never would have been made
*/
/*
If pending has not made changes to the form data, the pending record can be deleted as it never would have been made
*/
delete from cif.form_change
where project_revision_id = pending_project_revision_id
and form_data_table_name = fc.form_data_table_name
Expand Down

0 comments on commit 5483b43

Please sign in to comment.