1. 13 7月, 2016 1 次提交
  2. 02 7月, 2016 2 次提交
  3. 01 7月, 2016 2 次提交
  4. 30 6月, 2016 3 次提交
  5. 29 6月, 2016 1 次提交
  6. 23 6月, 2016 2 次提交
  7. 22 6月, 2016 2 次提交
  8. 18 6月, 2016 1 次提交
  9. 14 6月, 2016 4 次提交
  10. 11 6月, 2016 4 次提交
  11. 31 5月, 2016 1 次提交
    • S
      Ensure hashes can be passed to attributes using `composed_of` (#25212) · 0d5d8594
      Sean Griffin 提交于
      This behavior was broken by 36e9be85. When the value is assigned
      directly, either through mass assignment or directly assigning a hash,
      the hash gets passed through to this writer method directly. While this
      is intended to handle certain cases, when an explicit converter has been
      provided, we should continue to use that instead. The positioning of the
      added guard caused the new behavior to override that case.
      
      Fixes #25210
      0d5d8594
  12. 28 5月, 2016 6 次提交
  13. 25 5月, 2016 1 次提交
  14. 21 5月, 2016 1 次提交
  15. 19 5月, 2016 2 次提交
  16. 12 5月, 2016 2 次提交
  17. 11 5月, 2016 2 次提交
    • A
      Merge pull request #24978 from voray/reload-ar-cache-after-migrations-backport · bfa6eeda
      Arthur Nogueira Neves 提交于
      Make 'migrate' clear the schema cache afterward
      bfa6eeda
    • C
      Make 'migrate' clear the schema cache afterward · 94d93851
      Chris Arcand 提交于
      Without clearing the caches afterward, removals done in migrations would
      not be reflected in a separate task in the same process. That is, given
      a table with a migration to remove a column, the schema cache would
      still reflect that a table has that in something such as the
      'db:seed' task:
      
      `rake db:migrate db:seed`
      (A common thing to do in a script for a project ala `bin/setup`)
      
      vs
      
      `rake db:migrate && rake db:seed`
      (Two processes)
      
      The first would not reflect that the column was removed.
      The second would (cache reset).
      94d93851
  18. 01 5月, 2016 2 次提交
    • J
      Merge pull request #24797 from vipulnsward/backport-21950 · 54558b94
      Jeremy Daer 提交于
      Backport #21950
      54558b94
    • R
      Backport #21950 : · 2c894cb3
      Rafael Sales 提交于
      Fix generated projection fields in group by query
      
      Closes #21922
      
      Let `Book(id, author_id)`, `Photo(id, book_id, author_id)` and `Author(id)`
      
      Running `Book.group(:author_id).joins(:photos).count` will produce:
      
      * Rails 4.2 - conflicts `author_id` in both projection and group by:
      ```sql
      SELECT COUNT(*) AS count_all, author_id AS author_id
        FROM "books" INNER JOIN "photos" ON "photos"."book_id" = "books"."id"
       GROUP BY author_id
      ```
      
      * Master (9d02a25d) - conflicts `author_id` only in projection:
      ```sql
      SELECT COUNT(*) AS count_all, author_id AS author_id
        FROM "books" INNER JOIN "photos" ON "photos"."book_id" = "books"."id"
       GROUP BY "books"."author_id"
      ```
      
      * With this fix:
      ```sql
      SELECT COUNT(*) AS count_all, "books"."author_id" AS books_author_id
        FROM "books" INNER JOIN "photos" ON "photos"."book_id" = "books"."id"
       GROUP BY "books"."author_id"
      ```
      2c894cb3
  19. 26 4月, 2016 1 次提交
    • A
      Do not cache ActiveSupport::TimeZone#utc_offset · a611a813
      Alexey Shein 提交于
      This can be an issue when TZInfo::TimeZone#current_period is refreshed
      due to timezone period transition, but it's not reflected in
      ActiveSupport::TimeZone object.
      
      For example, on Sun, 26 Oct 2014 22:00 UTC, Moscow changed its TZ from
      MSK +04:00 to MSK +03:00 (-1 hour). If ActiveSupport::TimeZone['Moscow']
      happens to be initialized just before the timezone transition, it will
      cache its stale utc_offset even after the timezone transition.
      
      This commit removes cache and fixes this issue.
      Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
      a611a813