Improve performance of patient finder with tags on large DB

[kchapple]

On a large DB, the join on the tf_patient_tags pivot table caused big performance penalty, so I added a migration to insert an index to pid col of tf_patient_tags pivot table.

[kchapple]

This is really the only code. Migrations are only run once. There is no need for conditional logic in this case.

[aethelwulffe]

Does the migration require any user input to run?

[kchapple]

No, these migrations are run automatically. Essentially, the first request made to the server, the migration will be run. The system keeps track of the migrations that are run so they are only run once. Ken kenchapple.com facebook.com/kenchapplemusic @ken_chapple Check out my latest CD, Crossing the Black here: https://open.spotify.com/album/1fM4v6hJ1275fywjaREzNP?si=ohHDH2vV

…

On Aug 27, 2018, at 8:58 PM, Art Eaton ***@***.***> wrote: @aethelwulffe commented on this pull request. In interface/tags_filters/migrations/Migration_2018_08_22_14_48_11.php: > +-- behavior: The block will be executed if both statements below are true: +-- 1) The table table_name does not have a row where colname = value AND colname2 = value2. +-- 2) The table table_name does not have a row where colname = value AND colname3 = value3. + +-- #IfNotIndex +-- desc: This function will allow adding of indexes/keys. +-- arguments: table_name colname +-- behavior: If the index does not exist, it will be created + +-- #EndIf +-- all blocks are terminated with and #EndIf statement. + +-- +-- Indexes for table `tf_patients_tags` +-- + Does the migration require any user input to run? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.