-
Notifications
You must be signed in to change notification settings - Fork 99
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
(proposal) Move MySQL triggers into separate triggers.sql file #753
Labels
Comments
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Sep 28, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Sep 28, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
4 tasks
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Sep 30, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Oct 1, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Oct 4, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Oct 5, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Oct 6, 2016
This commit creates a table that contains a mapping between entity uuids and their human readable text. All updates to this table are made via triggers, leaving the controller code on both the server and the client the same. The entities are: 1. Suppliers 2. Employees 3. Patients NOTE that entities are both creditors and debtors. Another table will be made for documents (vouchers, invoices, payments, etc). I've moved all triggers into triggers.sql. Closes IMA-WorldHealth#753. Closes IMA-WorldHealth#629. Partially addresses IMA-WorldHealth#630.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To better navigate our codebase, it would be helpful to move all our triggers out into a separate
triggers.sql
file similar to theprocedures.sql
file.The text was updated successfully, but these errors were encountered: