##// END OF EJS Templates
api: pull-requests, fixed invocation of merge as another user.
api: pull-requests, fixed invocation of merge as another user.

File last commit:

r3290:ac4e4e5a default
r3481:b5202911 default
Show More
32 lines | 1.2 KiB | text/x-rst | RstLexer



We do not recommend using SQLite in a large development environment as it has an internal locking mechanism which can become a performance bottleneck when there are more than 5 concurrent users.

|RCE| installs SQLite as the default database if you do not specify another during installation. SQLite is suitable for small teams, projects with a low load, and evaluation purposes since it is built into |RCE| and does not require any additional database server.

Using MySQL or PostgreSQL in an large setup gives you much greater performance, and while migration tools exist to move from one database type to another, it is better to get it right first time and to immediately use MySQL or PostgreSQL when you deploy |RCE| in a production environment.

Migrating From SQLite to PostgreSQL

If you started working with SQLite and now need to migrate your database to PostgreSQL, you can contact support@rhodecode.com for some help. We have a set of scripts that enable SQLite to PostgreSQL migration. These scripts have been tested, and work with PostgreSQL 9.1+.


There are no SQLite to MySQL or MariaDB scripts available.