REFACTOR(DB): Patient reference calculation moved to MySQL #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Moves reference calculation from an additional controller transaction step into a TRIGGER performed BEFORE a patient insert. This method of calculating references delimited by project will allow any tables to include this column without adding additional overhead in the codebase.
jniles
changed the title
|
LGTM. |
jniles
added a commit
that referenced
this pull request
Jan 7, 2016
REFACTOR(DB): Patient reference calculation moved to MySQL
sfount
added a commit
to sfount/bhima-2.X
that referenced
this pull request
Dec 22, 2016
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
jniles
referenced
this pull request
in jniles/bhima
Dec 24, 2016
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
jniles
referenced
this pull request
in jniles/bhima
Dec 27, 2016
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
sfount
added a commit
to sfount/bhima-2.X
that referenced
this pull request
Dec 30, 2016
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
sfount
added a commit
to sfount/bhima-2.X
that referenced
this pull request
Dec 30, 2016
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
jniles
referenced
this pull request
in jniles/bhima
Jan 3, 2017
This commit introduces the proposed barcode string standard for receipt barcodes. This has been tested on the patient invoice receipt.
bors bot
added a commit
that referenced
this pull request
Dec 15, 2017
2320: Update pump to the latest version 🚀 r=jniles a=greenkeeper[bot] ## Version **2.0.0** of [pump](https://github.com/mafintosh/pump) was just published. <table> <tr> <th align=left> Dependency </td> <td> pump </td> </tr> <tr> <th align=left> Current Version </td> <td> 1.0.3 </td> </tr> <tr> <th align=left> Type </td> <td> devDependency </td> </tr> </table> The version **2.0.0** is **not covered** by your **current version range**. If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update. It might be worth looking into these changes and trying to get this project onto the latest version of pump. If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update. --- <details> <summary>Commits</summary> <p>The new version differs by 2 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/mafintosh/pump/commit/e3d0c444ceef59ff694c753303a35052e60b5186"><code>e3d0c44</code></a> <code>2.0.0</code></li> <li><a href="https://urls.greenkeeper.io/mafintosh/pump/commit/0c507239810b1e7f79ba0927ef78e90dd3a529e5"><code>0c50723</code></a> <code>(breaking) remove return of pipeline - closes #9 (#18)</code></li> </ul> <p>See the <a href="https://urls.greenkeeper.io/mafintosh/pump/compare/28557d8349d8e3b6878f9955d28b4a52c6a44de3...e3d0c444ceef59ff694c753303a35052e60b5186">full diff</a></p> </details> <details> <summary>FAQ and help</summary> There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new). </details> --- Your [Greenkeeper](https://greenkeeper.io) bot 🌴
bors bot
added a commit
that referenced
this pull request
Apr 16, 2019
3680: Update tempy to the latest version 🚀 r=jniles a=greenkeeper[bot] ## The dependency [tempy](https://github.com/sindresorhus/tempy) was updated from `0.2.1` to `0.3.0`. This version is **not covered** by your **current version range**. If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update. --- <details> <summary>Release Notes for v0.3.0</summary> <p>Breaking:</p> <ul> <li>Require Node.js 8 <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/sindresorhus/tempy/commit/a168b8dc4f050fe08a5266a06969564dc80e950c/hovercard" href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/a168b8dc4f050fe08a5266a06969564dc80e950c"><tt>a168b8d</tt></a></li> </ul> <p>Enhancements:</p> <ul> <li>Add TypeScript definition (<a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="432898666" data-permission-text="Issue title is private" data-url="sindresorhus/tempy#9" data-hovercard-type="pull_request" data-hovercard-url="/sindresorhus/tempy/pull/9/hovercard" href="https://urls.greenkeeper.io/sindresorhus/tempy/pull/9">#9</a>) <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/sindresorhus/tempy/commit/2e2760e02f5f4c7431f45740636b24f88bcbae2f/hovercard" href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/2e2760e02f5f4c7431f45740636b24f88bcbae2f"><tt>2e2760e</tt></a></li> </ul> <p><a class="commit-link" href="https://urls.greenkeeper.io/sindresorhus/tempy/compare/v0.2.1...v0.3.0"><tt>v0.2.1...v0.3.0</tt></a></p> </details> <details> <summary>Commits</summary> <p>The new version differs by 5 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/8958de57554b06f1dceff8cd5f969aee57e0e056"><code>8958de5</code></a> <code>0.3.0</code></li> <li><a href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/a168b8dc4f050fe08a5266a06969564dc80e950c"><code>a168b8d</code></a> <code>Require Node.js 8</code></li> <li><a href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/2e2760e02f5f4c7431f45740636b24f88bcbae2f"><code>2e2760e</code></a> <code>Add TypeScript definition (#9)</code></li> <li><a href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/ca90766551de5ba8e9d727ddf3d86ba0949f2e88"><code>ca90766</code></a> <code>Require Node.js 6</code></li> <li><a href="https://urls.greenkeeper.io/sindresorhus/tempy/commit/14edc260107351df453adad649e4cad0e2b5104f"><code>14edc26</code></a> <code>Minor code improvements and increased test coverage (#7)</code></li> </ul> <p>See the <a href="https://urls.greenkeeper.io/sindresorhus/tempy/compare/ec634c9e48a6feca53b70fcd0fbe80db5c5682b8...8958de57554b06f1dceff8cd5f969aee57e0e056">full diff</a></p> </details> <details> <summary>FAQ and help</summary> There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new). </details> --- Your [Greenkeeper](https://greenkeeper.io) bot 🌴 Co-authored-by: greenkeeper[bot] <greenkeeper[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moves reference calculation from an additional controller transaction
step into a TRIGGER performed BEFORE a patient insert. This method of
calculating references delimited by project will allow any tables to
include this column without adding additional overhead in the codebase.