Skip to content
Snippets Groups Projects
  1. Sep 24, 2019
  2. Sep 11, 2019
  3. Aug 22, 2019
  4. Aug 16, 2019
  5. Jul 08, 2019
  6. Jun 19, 2019
  7. May 27, 2019
  8. May 22, 2019
  9. May 20, 2019
  10. May 05, 2019
  11. Apr 23, 2019
  12. Feb 22, 2019
  13. Feb 18, 2019
  14. Jan 08, 2019
  15. Sep 21, 2018
  16. Jun 06, 2018
  17. May 14, 2018
  18. Mar 01, 2018
  19. Jan 19, 2018
  20. Nov 28, 2017
  21. Nov 14, 2017
  22. Aug 07, 2017
  23. Jul 13, 2017
  24. May 03, 2017
  25. Mar 22, 2017
  26. Feb 10, 2017
  27. Nov 03, 2016
  28. Aug 05, 2016
  29. Jul 18, 2016
  30. Jun 23, 2016
  31. 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
  32. Oct 31, 2015
  33. Sep 03, 2015
  34. Dec 04, 2014
  35. Jul 31, 2014
  36. Apr 24, 2014
Loading