##// END OF EJS Templates
api: comment_pull_request, added commit_id parameter to validate status changed on particular commit....
api: comment_pull_request, added commit_id parameter to validate status changed on particular commit. - when using the API and creating a comment with status change it's now possible to pass in commit_id, this will allow validation if status change of pull_request is allowed based on the given commit_id. This solves the case when long running test sends approval of pull request which was already updated several times. The commit_id will now validate for which state the approval was made, and prevent accidental aproval of outdated pull requests.

File last commit:

r1:854a839a default
r1269:26e59d48 default
Show More
using-sqllite.rst
32 lines | 1.2 KiB | text/x-rst | RstLexer

SQLite

Important

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.

|RCM| 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 |RCM| 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 |RCM| 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+.

Note

There are no SQLite to MySQL or MariaDB scripts available.