DPL-047 Use stored procedure to retrieve destination plate information
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
User story
As a development team we would like to change how we query the DART database to retrieve the destination plate information. We are using currently using a view but the view is not operating efficiently and can lead to blocking issues. A stored procedure should operate most efficiently and provide the same, required output.
Who are the primary contacts for this story
@pjvv
@andrewsparkes
Acceptance criteria
To be considered successful the solution must allow:
- call a stored procedure instead of the view
Dependencies
This story is blocked by the following dependencies:
- #<issue_no.>
- sanger/#<issue_no.>
References
This story has a non-blocking relationship with:
- #<issue_no.>
- sanger/#<issue_no.>
Additional context
Yann will be assisting from the DBA team to convert the view to a stored procedure and help us optimise the interactions between LIMS and SQL Server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the Lighthouse code that retrieves destination plate information through the current view and review its SQL Server interaction; confirm the stored procedure returns the same required output and that the query path calls it instead of the view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100