Skip to content
Snippets Groups Projects
Select Git revision
  • 60d005f8d174d21162cab2b029f74cfe2925acab
  • ballinvoher default protected
  • client-http-server-for-token
  • master
  • gitlab-auth-issue
  • windows
  • microsoft
  • message
  • azure_auth
  • prometheus
  • permission-templates
  • no-datastore
  • save-public-keys
  • gitlab-group-level-start
  • v1.1.0
  • v1.0.0
  • v0.1
17 results

server

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Niall Sheridan authored
    In retrospect a primary key that has no relation to the certificate is preferred to using the certificate KeyID. The KeyID is also very large for a primary index.
    This is a moderately tricky migration, especially for SQLite which has no means of altering the table in this fashion - it involves creating the new table and copying the data.
    Order of commands also matters - index names are global in SQLite, so the `idx_expires_at` index needs to be created at the correct stages.
    
    For MySQL migration the necessary steps are run as a single alter statement to minimise the risk of leaving the migration in an incomplete state if anything aborts.
    
    When tested on a table with 250,000 rows (MySQL 5.7) the migration took 3 seconds to complete. As certificates will be requested infrequently the risk of prolonged locking is minimal.
    60d005f8
    History
    Name Last commit Last update
    ..