Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Schedule A/B parent tables should not have any data #2652

Closed
vrajmohan opened this issue Sep 12, 2017 · 2 comments
Closed

Schedule A/B parent tables should not have any data #2652

vrajmohan opened this issue Sep 12, 2017 · 2 comments
Assignees
@vrajmohan
Labels
Bug
Milestone
Sprint 3.6

Comments

@vrajmohan
Copy link
Contributor

Schedules A and B tables are partitioned by two_year_transaction_period and are designed to not have any data in them (all data should be in the partitions). However they do contain data. This needs to be investigated and fixed.
@vrajmohan vrajmohan changed the title Bug - Schedule A/B parent tables should not have any data Schedule A/B parent tables should not have any data Sep 12, 2017
@vrajmohan vrajmohan added this to the Sprint 3.6 milestone Sep 12, 2017
@vrajmohan
Copy link
Contributor Author

vrajmohan commented Sep 12, 2017 •
edited
Loading

The main cause is that the trigger that handles inserting into the right partition table (BEFORE INSERT ON _ FOR EACH ROW EXECUTE PROCEDURE insert_sched_master) has gone AWOL.

FYI, @LindsayYoung, @ccostino.

@vrajmohan vrajmohan self-assigned this Sep 13, 2017
@vrajmohan
Copy link
Contributor Author

The culprit was a strip_triggers function. It has been removed in https://github.com/18F/openFEC/pull/2664.

@patphongs patphongs mentioned this issue Mar 4, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vrajmohan vrajmohan

Labels
Bug
Projects
None yet
Milestone
Sprint 3.6
Development

No branches or pull requests
2 participants
@vrajmohan @LindsayYoung