3 ms·

Hi! Author in question here, if anybody would like to know more about this particular feature I'll be happy to answer any questions. The changes discussed in th

• koolba 11y ago
  Why bother supporting both MySQL and Postgres for the backend? Wouldn't picking one (~cough~ Postgres) simplify things? From my experience, attempting to support multiple backend stores leads to either crippled functionality, i.e. lowest common denominator CRUD usage, or lots of messy if/then logic to use DB specific features.
  • YorickPeterse 11y ago
    Personally I'd love to drop support for MySQL but we have a few too many organizations that only run MySQL _and_ want to use GitLab. It would be a waste if said organizations wouldn't be able to use GitLab. The approach I tend to go with is to make queries perform as good as possible on PostgreSQL without using too many PostgreSQL specific bits (which would make supporting both DBs more difficult), while making sure they still perform good enough on MySQL.
  • jobvandervoort 11y ago
    To add to Yoricks comment: Many of our customers have large MySQL clusters running. It's very convenient to be able to just plug GitLab into that. We have no intention in dropping it in the near future. For instance, our Pivotal Cloud Foundry (PCF) tile makes use of the MySQL cluster in PCF [0]. For those reasons, we'll continue to support MySQL and make sure it's performant. [0]: http://docs.pivotal.io/gitlab/ http://docs.pivotal.io/gitlab/