- 11 Mar, 2016 40 commits
-
-
Yorick Peterse authored
This ensures searching namespaces works exactly the same as searching for any other resource.
-
Yorick Peterse authored
We can just use "arel_table" in these cases instead of "SomeClass.arel_table".
-
Yorick Peterse authored
-
Yorick Peterse authored
We don't need the extra layer of nesting of UNION queries here (as User#authorized_projects already returns a UNION'd query).
-
Yorick Peterse authored
There's no need to order queries used as sub-queries and doing so can add potential overhead.
-
Yorick Peterse authored
This ensures some other methods such as the "issues" method still work.
-
Yorick Peterse authored
This spec was still passing an ID to the #initialize method instead of a Project instance.
-
Yorick Peterse authored
This code is mostly a copy-paste from existing pull requests so there's no point in running Rubocop on it.
-
Yorick Peterse authored
This ensures that options such as `using: :gin` and PostgreSQL operator classes are ignored when loading a schema into a MySQL database.
-
Yorick Peterse authored
This also includes e.g. the appearances table which apparently wasn't already included in the schema.
-
Yorick Peterse authored
This is needed to support creating/dumping/loading indexes that use the gin_trgm_ops operator class on PostgreSQL. These changes are taken from Rails pull request https://github.com/rails/rails/pull/19090.
-
Yorick Peterse authored
Previously this class would be given a project ID which was then used to retrieve the corresponding Project object. However, in all cases the Project object was already known as it was used to grab the ID to pass to ProjectSearchResults. By just passing a Project instead we remove the need for an extra query as well as the need for some other complexity in this class.
-
Yorick Peterse authored
This removes the need for plucking snippet IDs into memory.
-
Yorick Peterse authored
Instead of plucking IDs this class now uses ActiveRecord::Relation objects. Plucking IDs is problematic as searching for projects can lead to a huge amount of IDs being loaded into memory only to be used as an argument for another query (instead of just using a sub-query).
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
Previously this used a regular LIKE which is case-sensitive on PostgreSQL. This ensures that for both PostgreSQL and MySQL the searching is case-insensitive similar to searching for projects.
-
Yorick Peterse authored
Similar to the changes made to Project.search the method Project.search_by_title now also uses Arel so it can automatically use ILIKE/LIKE instead of the lower() function.
-
Yorick Peterse authored
This chance is broken up in two steps: 1. Use ILIKE on PostgreSQL and LIKE on MySQL, instead of using "WHERE lower(x) LIKE lower(y)" as ILIKE is significantly faster than using lower(). In many cases the use of lower() will force a slow sequence scan. 2. Instead of using 1 query that searches both projects and namespaces using a JOIN we're using 2 separate queries that are UNION'd together. Using a JOIN would force a slow sequence scan, using a UNION avoids this. This method now uses Arel as Arel automatically uses ILIKE on PostgreSQL and LIKE on MySQL, removing the need to handle this manually.
-
Yorick Peterse authored
This allows the LIKE condition to use an index. Without a GIN + trigram index LIKE queries using a wildcard at the start _won't_ use an index and instead perform a sequence scan.
-
Robert Speicher authored
Move group activity feed to separate page for consistency with dashboard and project pages Fixes #14161. Part of #13480 See merge request !3157
-
Achilleas Pipinellis authored
Fix incorrect gitlab.rb variable in CI docs Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/14115 See merge request !3187
-
Achilleas Pipinellis authored
[ci skip]
-
Jacob Schatz authored
Improved search results filter dropdown ## Current Currently filter dropdowns on search results page can be **very** long and off the page ![Screen_Shot_2016-03-11_at_15.25.24](/uploads/3418b0a6f4f8a0a8bd2441b53502c574/Screen_Shot_2016-03-11_at_15.25.24.png) ## New Changed over to the new dropdown ![Screen_Shot_2016-03-11_at_15.29.06](/uploads/2d3a4a9b3e50f3e0fc1748a026cd5905/Screen_Shot_2016-03-11_at_15.29.06.png) See merge request !3183
-
Patricio Cano authored
Upgrade `omniauth-saml` to 1.5.0 and document it's new capabilities. With this MR I'm upgrading `omniauth-saml` to 1.5.0 to include new and improved functionality. See https://github.com/omniauth/omniauth-saml/blob/master/CHANGELOG.md for more details. This MR includes new documentation, so @axil can you also take a look? /cc @DouweM See merge request !3170
-
Patricio Cano authored
[ci skip]
-
Phil Hughes authored
-
Jacob Schatz authored
Updated UI of award emoji Closes #13878 See merge request !3028
-
Phil Hughes authored
-
Douwe Maan authored
Removed benchmark suite and its documentation Related issue: gitlab-org/gitlab-ce#13718 See merge request !3137
-
Douwe Maan authored
Updated gitlab_git to 9.0.1 This includes gitlab-org/gitlab_git!69 and will hopefully solve gitlab-org/gitlab-ce#13808. See merge request !3123
-
Jacob Schatz authored
Fixes issue with issue sidebar toggle button not working Closes #14195 See merge request !3165
-
Jacob Schatz authored
Account settings Closes #13854 ![](https://gitlab.com/gitlab-org/gitlab-ce/uploads/4802a7b4f74f17d25a611ed1a2200445/account-settings.png) See merge request !3039
-
Jacob Schatz authored
Added discard button to comment form Also changed the labels on the buttons to better match the action they are completing. Closes #8057 See merge request !3085
-
Dmitriy Zaporozhets authored
Add error for ajax:error when submitting comments Fixes #13814 ![Screen_Shot_2016-02-25_at_1.54.56_PM](/uploads/d70d706d306079df1b00d70f09affb63/Screen_Shot_2016-02-25_at_1.54.56_PM.png) cc @dblessing See merge request !2976
-
Kamil Trzciński authored
Support YAML alias/anchor usage in .gitlab-ci.yml This allows to reuse one job as a template for another one: ``` job1: &JOBTMPL script: execute-script-for-job job2: *JOBTMPL ``` This also helps to solve some of the issues in gitlab-org/gitlab-ci#342 See merge request !2958
-