An error occurred fetching the project authors.
  1. 02 Mar, 2020 1 commit
  2. 06 Feb, 2020 1 commit
  3. 26 Dec, 2019 1 commit
  4. 13 Dec, 2019 1 commit
  5. 01 Dec, 2019 1 commit
  6. 22 Oct, 2019 1 commit
  7. 04 Oct, 2019 2 commits
  8. 27 Sep, 2019 1 commit
  9. 18 Sep, 2019 2 commits
  10. 04 Sep, 2019 1 commit
  11. 27 Aug, 2019 1 commit
    • Mayra Cabrera's avatar
      Migrations guide: use atomic steps, when possible · 9d5ea420
      Mayra Cabrera authored
      Currently, the DB migrations guide says that "you must" use non-blocking
      operations (such as CREATE INDEX CONCURRENTLY), always.
      
      But this does not make sense in cases of empty tables and leads to
      splitting the work to multiple non-atomic
      (with disable_ddl_transaction!) DB migrations.
      
      To follow KISS principle, to have fewer DB migrations steps,
      to have them atomic when it's possible and simplify deployment
      and troubleshooting, the following exceptions were added
      to the doc:
      
      - index creation,
      - index dropping,
      - defining an FK,
      - adding a column with DEFAULT,
      9d5ea420
  12. 09 Aug, 2019 1 commit
  13. 25 Jul, 2019 1 commit
  14. 19 Jul, 2019 1 commit