Skip to content
Snippets Groups Projects

Remove SQLite support

Merged gitlab-qa-bot requested to merge github/fork/riyad/remove-sqlite into master

Created by: riyad

Supporting SQLite makes no sense for GitLab:

  • SQLite shouldn't be used in production (because of mulit-user/multi-process access to DB)
  • Strange race conditions with SQL (e.g. #1262 (closed))
  • Problems with locking

It might be a good idea for starting development, but it shouldn't be supported in production.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Created by: sodabrew

    Why? Please don't drop sqlite.

    By Administrator on 2012-11-28T20:40:47 (imported from GitLab project)

    By Administrator on 2012-11-28T20:40:47 (imported from GitLab)

  • Created by: riyad

    Because SQLite is not made for mulit-user/multi-process access which is almost always the case in production env. In contrast to MySQL or PostgreSQL there is no database process that an app can connect to which manages concurrent access to the data, but they have to "directly" (actually through the SQLite driver) manipulate the SQLite database file. SQLite is made for embedding DBs in apps where you can make sure there is only one process accessing the DB. A web server is not such an environment.

    By Administrator on 2012-11-30T16:22:33 (imported from GitLab project)

    By Administrator on 2012-11-30T16:22:33 (imported from GitLab)

  • Created by: dzaporozhets

    :thumbsup:

    By Administrator on 2012-11-30T16:27:14 (imported from GitLab project)

    By Administrator on 2012-11-30T16:27:14 (imported from GitLab)

  • Created by: mrohnstock

    I'm currently using gitlab with two other developers and haven't any problems with sqlite3 yet. For bigger teams I would suggest to mysql/postgresql, but for smaller teams, sqlite3 is more than enough, isn't it?

    Please reconsider this change :(

    By Administrator on 2012-12-20T20:27:59 (imported from GitLab project)

    By Administrator on 2012-12-20T20:27:59 (imported from GitLab)

  • Created by: koenpunt

    Migrating from sqlite to mysql is easy, using rails migrations. For an example on how to do this you can have look at this question at Stack Overflow

    By Administrator on 2012-12-21T01:00:48 (imported from GitLab project)

    By Administrator on 2012-12-21T01:00:48 (imported from GitLab)

  • Created by: koenpunt

    I also stumbled upon a page in the wiki about migrating: https://github.com/gitlabhq/gitlabhq/wiki/Migrate-from-SQLite-to-MySQL

    By Administrator on 2012-12-21T01:27:06 (imported from GitLab project)

    By Administrator on 2012-12-21T01:27:06 (imported from GitLab)

  • Created by: mrohnstock

    Thanks for the links, but I know for sure, how to migrate from sqlite to mysql.

    Using gitlab with mysql for a small team is just oversized, sqlite3 would fit there much better.

    By Administrator on 2012-12-21T08:15:56 (imported from GitLab project)

    By Administrator on 2012-12-21T08:15:56 (imported from GitLab)

Please register or sign in to reply
Loading