- 28 2月, 2013 1 次提交
-
-
由 Steve Klabnik 提交于
This reverts commit 408227d9, reversing changes made to dca0b57d.
-
- 26 2月, 2013 1 次提交
-
-
由 Yves Senn 提交于
Fixes #9275. When `#order` is called with a Symbol this patch will prepend the quoted_table_name. Before the postgresql adapter failed to build queries containg a join and an order with a symbol. This expansion happens for all adapters.
-
- 25 2月, 2013 2 次提交
-
-
由 Rafael Mendonça França 提交于
Taking the wise advice of @carlosantoniodasilva
-
由 Yves Senn 提交于
We discussed that the auto explain feature is rarely used. This PR removes only the automatic explain. You can still display the explain output for any given relation using `ActiveRecord::Relation#explain`. As a side-effect this should also fix the connection problem during asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie` forced a connection.
-
- 24 2月, 2013 1 次提交
-
-
由 Xavier Noria 提交于
-
- 21 2月, 2013 3 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
由 wangjohn 提交于
The function is now called has_arguments? so that it's easier to tell that it's just checking to see if the args are blank or not.
-
- 20 2月, 2013 2 次提交
-
-
由 wangjohn 提交于
for query methods in a where_clause. Also, modified the CHANGELOG entry because it had false information and added tests.
-
由 John J Wang 提交于
-
- 16 2月, 2013 1 次提交
-
-
由 Vijay Dev 提交于
-
- 10 2月, 2013 1 次提交
-
-
由 robertomiranda 提交于
-
- 09 2月, 2013 2 次提交
-
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
- 08 2月, 2013 6 次提交
-
-
由 robertomiranda 提交于
-
由 robertomiranda 提交于
-
由 Maurizio De Santis 提交于
-
由 Maurizio De Santis 提交于
-
由 Maurizio De Santis 提交于
-
由 Maurizio De Santis 提交于
-
- 07 2月, 2013 1 次提交
-
-
由 Dylan Smith 提交于
-
- 28 1月, 2013 1 次提交
-
-
由 Jon Leighton 提交于
This caused a bug with the new associations implementation, because now association conditions are represented as Arel nodes internally right up to when the whole thing gets turned to SQL. In Rails 3.2, association conditions get turned to raw SQL early on, which prevents Relation#merge from interfering. The current implementation was buggy when a default_scope existed on the target model, since we would basically end up doing: default_scope.merge(association_scope) If default_scope contained a where(foo: 'a') and association_scope contained a where(foo: 'b').where(foo: 'c') then the merger would see that the same column is representated on both sides of the merge and collapse the wheres to all but the last: where(foo: 'c') Now, the RHS of the merge is left alone. Fixes #8990
-
- 26 1月, 2013 1 次提交
-
-
由 Yves Senn 提交于
closes #6865
-
- 25 1月, 2013 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 18 1月, 2013 3 次提交
-
-
由 Guillermo Iguaran 提交于
This reverts commit 637a7d9d, reversing changes made to 5937bd02.
-
由 robertomiranda 提交于
-
由 Carlos Antonio da Silva 提交于
There's no need to create a new arel table or reflect on the column association if the value is empty, these attributes are not used. Also no need to concat a new array, just append the query value.
-
- 07 1月, 2013 1 次提交
-
-
由 Akira Matsuda 提交于
* dependencies/autoload * concern * deprecation
-
- 01 1月, 2013 1 次提交
-
-
由 Angelo capilleri 提交于
-
- 30 12月, 2012 1 次提交
-
-
由 Arun Agrawal 提交于
-
- 29 12月, 2012 3 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 14 12月, 2012 1 次提交
-
-
由 thedarkone 提交于
Summary of the changes: * Add thread_safe gem. * Use thread safe cache for digestor caching. * Replace manual synchronization with ThreadSafe::Cache in Relation::Delegation. * Replace @attribute_method_matchers_cache Hash with ThreadSafe::Cache. * Use TS::Cache to avoid the synchronisation overhead on listener retrieval. * Replace synchronisation with TS::Cache usage. * Use a preallocated array for performance/memory reasons. * Update the controllers cache to the new AS::Dependencies::ClassCache API. The original @controllers cache no longer makes much sense after @tenderlove's changes in 7b6bfe84 and f345e238. * Use TS::Cache in the connection pool to avoid locking overhead. * Use TS::Cache in ConnectionHandler.
-
- 09 12月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
* Fix example queries * Remove doc entries of where.like/not_like. * Remove :chain from where.not related docs. To me that's an implementation detail and we don't expect people to use where(:chain).not.
-
- 08 12月, 2012 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
The real win with these chain methods is where.not, that takes care of different scenarios in a graceful way, for instance when the given value is nil. where("author.id != ?", author_to_ignore.id) where.not("author.id", author_to_ignore.id) Both where.like and where.not_like compared to the SQL versions doesn't seem to give us that much: Post.where("title LIKE 'ruby on%'") Post.where.like(title: 'ruby on%'") Post.where("title NOT LIKE 'ruby on%'") Post.where.not_like(title: 'ruby on%'") Thus Rails is adding where.not, but not where.like/not_like and others.
-
由 claudiob 提交于
This commit stems from https://github.com/rails/rails/pull/8332#issuecomment-11127957 Since the formats in which conditions can be passed to `not` differ from the formats in which conditions can be passed to `like` and `not_like`, then I think it's worth adding rdoc and tests to show this behavior
-
- 07 12月, 2012 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
Arel::Nodes::In inherits from Arel::Nodes::Equality, so the case statement was always using the Equality operator for both scenarios, resulting in a not equal query instead.
-
由 claudiob 提交于
This commit updates the rdoc of AR#where to match the changes applied in https://github.com/rails/rails/commit/6ba0f97 that is: * `where(nil)` has the same effect of `where('')`: a no op * `where` (no args) has the same effect of `where(:chain)`: to create a WhereChain
-