Store Human Readable references in debtor/creditor tables
#629
Assignees
Labels
Comments
jniles
changed the title
debtor/creditor tables.debtor/creditor tables
|
I'll take this one. |
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
4 tasks
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
jniles
referenced
this issue
in jniles/bhima
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 Third-Culture-Software#753. Closes #629. Partially addresses #630.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to facilitate easy lookups of the debtor/creditor ids in the vouchers and journal tables, I propose that we store the human readable ids in the
debtor/creditortables. The only change is add a single text columnreferencethat storesTPA1,TPA304, etc, as the debtor or creditor's human-readable ID.The text was updated successfully, but these errors were encountered: