Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
1 second
Duration
3 minutes
Labels
None
Revisions
Git
9d006ec0157dd50b4d75e2640a7428aacd4e1803 9d006ec0157dd50b4d75e2640a7428aacd4e1803
Release scripts
a72ca16daff268573032d8bd52a15be883f08322 a72ca16daff268573032d8bd52a15be883f08322
Total tests
452
Successful since
#305 ()

Tests

  • 0 New failures
  • 0 Existing failures
  • 0 Fixed

Code commits

Git
Author Commit Message Commit date
Ivo Ulrich <teleivo@users.noreply.github.com> Ivo Ulrich <teleivo@users.noreply.github.com> 9d006ec0157dd50b4d75e2640a7428aacd4e1803 9d006ec0157dd50b4d75e2640a7428aacd4e1803 Merge pull request #454 from teleivo/radordertable-fix
Remove radiology_order.order_id autoIncrement
teleivo <mrteleivo@gmail.com> teleivo <mrteleivo@gmail.com> f52d973449b2fccfb230e603a862be9e7232019b f52d973449b2fccfb230e603a862be9e7232019b Remove radiology_order.order_id autoIncrement
the radiology_order.order_id primary key was set to autoIncrement which makes
it possible to insert a new radiology_order using

"insert into radiology_order values (NULL);"

if there is a test_order matching the current auto_increment value of the
radiology_order. This should not be possible as this can cause a
radiology_order being attached to a test_order which is in fact not a
radiology_order.

Not-null constraint on radiology_order.order_id and Foreign key constraint to test_order.order_id
together ensure integrity of radiology_order data.