Skip to content
Snippets Groups Projects
  1. Jun 19, 2019
  2. May 27, 2019
  3. May 22, 2019
  4. May 20, 2019
  5. May 05, 2019
  6. Apr 23, 2019
  7. Feb 22, 2019
  8. Feb 18, 2019
  9. Jan 08, 2019
  10. Sep 21, 2018
  11. Jun 06, 2018
  12. May 14, 2018
  13. Mar 01, 2018
  14. Jan 19, 2018
  15. Nov 28, 2017
  16. Nov 14, 2017
  17. Aug 07, 2017
  18. Jul 13, 2017
  19. May 03, 2017
  20. Mar 22, 2017
  21. Feb 10, 2017
  22. Nov 03, 2016
  23. Aug 05, 2016
  24. Jul 18, 2016
  25. Jun 23, 2016
  26. Apr 14, 2016
    • Yorick Peterse's avatar
      Use rake db:reset instead of db:setup · a54af831
      Yorick Peterse authored
      Using db:reset ensures existing tables are first dropped. This in turn
      ensures that we can drop tables regardless of any foreign key
      constraints. While CE currently doesn't have any foreign keys EE defines
      the following relation:
      
          remote_mirrors.project_id -> projects.id
      
      MySQL will complain whenever you try to drop the "projects" table first
      even when using "DROP TABLE ... CASCADE".
      Verified
      a54af831
  27. Oct 31, 2015
  28. Sep 03, 2015
  29. Dec 04, 2014
  30. Jul 31, 2014
  31. Apr 24, 2014
Loading