- 15 2月, 2017 2 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 14 2月, 2017 13 次提交
-
-
由 Toon Claes 提交于
It consolidates these endpoints: - /projects - /projects/owned - /projects/visible - /projects/starred - /projects/all Into the /projects endpoint using query parameters.
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Lin Jen-Shin 提交于
This way we could reuse this pool for other migrations Feedback: * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8987#note_22923350 * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8987#note_22923365
-
由 wendy0402 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Oswaldo Ferreira 提交于
-
由 Mike Greiling 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Lin Jen-Shin 提交于
-
由 Yorick Peterse 提交于
We don't need to connect when requesting the name of the database adapter. This in turn should prevent us from requesting/leaking connections just by asking whether we're using PostgreSQL or MySQL.
-
由 Robert Speicher 提交于
-
- 13 2月, 2017 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 11 2月, 2017 3 次提交
-
-
由 Yorick Peterse 提交于
This method allows one to create foreign keys without blocking access to the source table, but only on PostgreSQL. When creating a regular foreign key the "ALTER TABLE" statement used for this won't return until all data has been validated. This statement in turn will acquire a lock on the source table. As a result this lock can be held for quite a long amount of time, depending on the number of rows and system load. By breaking up the foreign key creation process in two steps (creation, and validation) we can reduce the amount of locking to a minimum. Locking is still necessary for the "ALTER TABLE" statement that adds the constraint, but this is a fast process and so will only block access for a few milliseconds.
-
由 Alfredo Sumaran 提交于
This reverts commit b7c5ca49, reversing changes made to 9745c98b.
-
由 dixpac 提交于
Reason for renaming is to comply with naming convention of services in codebase.
-
- 10 2月, 2017 3 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Alfredo Sumaran 提交于
-
由 Joost Rijneveld 提交于
-
- 09 2月, 2017 2 次提交
-
-
由 James Edwards-Jones 提交于
-
由 Ershad Kunnakkadan 提交于
-
- 08 2月, 2017 6 次提交
-
-
由 Z.J. van de Weg 提交于
Given the the Issuable class will soon also have to support MRs this signals that it can only be used by issues.
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 dixpac 提交于
* Changed name of delete_user_service and worker to destroy * Move and change delete_group_service to Groups::DestroyService * Rename Notes::DeleteService to Notes::DestroyService
-
由 James Edwards-Jones 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 07 2月, 2017 10 次提交
-
-
由 Connor Shea 提交于
Cherry-picked 'Remove colorize methods that weren't in CE.'
-
由 Z.J. van de Weg 提交于
-
由 Toon Claes 提交于
The create and edit actions for projects had these parameters: - `public` (optional) - if true same as setting `visibility_level = 20` - `visibility_level` (optional) Remove the `public` parameter to avoid contradiction.
-
由 Robert Schilling 提交于
-
由 Drew Blessing 提交于
Cherry-picked ‘Fix syntax error in conditional statement’
-
由 Jarka Kadlecova 提交于
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
由 James Lopez 提交于
-
由 James Lopez 提交于
-