| Age | Commit message (Collapse) | Author |
|---|
|
Use the more robust `cursor.lastrowid` to get the row identifier
value, rather than using the `SELECT MAX(Id) …` form. With the
`cursor.lastrowid` form, we do not have to remember to add 1 to the
value to avoid conflict.
|
|
Previously `ProbeFreezeId` was set as 1 more than the largest `Id`
value found, which might not end up being the same as the incremented
Id.
This commit, thus, queries by `Id` which is more robust, and does an
actual update for the `ProbeFreezeId` column to make it same value as
`Id`.
|
|
|
|
|
|
|
|
|
|
To make `species_by_id` function reusable even outside of the
application context, pass in the database connection instead of
creating the connection inside the function.
|
|
Notify the user when they try to create a new dataset that has the
same name as an existing dataset and give them the chance to fix it
before continuing.
|
|
|
|
Due to possible schema differences between local small db on
development computer and those on CI/CD and Production, explicitly
specify the columns being operated on by the queries.
|
|
|
|
|
|
* Display the status of the job, as it is running
* Display STDERR output if an error occurs
* Display STDOUT output as job is running and on successful completion
of the job
|
|
- Hook up external data insertion script to webserver code
- Provide rudimentary status indication
- Generalise some job creation details
|
|
|
|
Provide user with a confirmation stage where they can verify all the
data before inserting into the database.
|
|
Enable the user to create a new dataset should the need arise.
A few extra fixes were done, such as:
- Provide list of average methods to choose from
- Provide input elements for some expected fields
- Add a new confirmation step before doing the actual data update
|
|
Rather than using the redirect, that led to exposing the study id as a
get parameter, this commit adds an auxilliary step that allows the
user to choose whether to continue with the new study or go back and
select an existing study.
|
|
- Implement UI enabling selection from existing datasets
- Start implementation of UI that enables creation of new dataset
|
|
Enable the creation of the new study, and redirect appropriately with
the new study id.
|
|
- Build code to populate the "Group" and "Tissue" dropdown lists
- Enable redirect with POST data (code 307) in case there is input
error to enable the user fix their errors
- Move hidden fields to macro to reduce repetition
|
|
Implement the select study UI
|
|
|
|
|
|
The filetype determines the queries to be run to update the database,
therefore, this commit adds filetype information.
|
|
The GeneChipId value is required for the data being inserted, so this
commit provides the UI to enable selection of the chip.
|
|
As part of updating the database with the new data, there is a need to
select the appropriate dataset that the data belongs to, and this
commit provides the UI to assist the user do that.
|
