-
-
Notifications
You must be signed in to change notification settings - Fork 403
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.
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
Add foreign key constraint for transaction.requisition_id #108
Comments
jmiranda
changed the title
Check whether transaction.requisition_id has foreign key constraint
Add foreign key constraint for transaction.requisition_id
Sep 18, 2015
jmiranda
added a commit
that referenced
this issue
May 6, 2016
jmiranda
added a commit
that referenced
this issue
May 6, 2016
jmiranda
added a commit
that referenced
this issue
May 10, 2016
* Hotfix 0.7.8 (#141) * minor cleanup to prevent the assign identifier quartz job from throwing hundreds of "Duplicate key" errors if the pool of identifiers is small enough to cause lots of collisions * removed unnecessarily verbose logging from inventory service * Purchase Order UI changes to make it more consistent with other pages * fixed #133: added ability to import order line items into an existing order; also added rollback feature * fixed #50: Illegal attempt to associate a collection with two open sessions when receiving against purchase order * Minor enhancements to make UI a little more consistent across entire app * bumped app version to 0.7.8 * removed annoying inventory sampling report constraint * fixed #89: made significant performances improvements to the dashboard * Removed errant text that was committed by accident * Hotfix/62 missing foreign key constraints (#145) * added missing primary keys and foreign key constraints to several tables (fixed #62, #108) * bumped app version to 0.7.9 * Fixed unit test for the show inventory report feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yesterday, I had to deal with an issue where PIH Liberia had deleted a requisition, but the transactions underlying that requisition were left intact including the deleted requisition_id (see OBPIH-349: Stock history viewing issue: JY51). The bug manifested itself by not allowing users to view the stock history for a product at a certain location. This is a blocker and should be dealt with immediately to prevent unintended loss of data.
The text was updated successfully, but these errors were encountered: