1. 18 8月, 2013 1 次提交
  2. 28 7月, 2013 1 次提交
    • N
      fix order dependent test · 09beb9c2
      Neeraj Singh 提交于
      `ReflectionTest` uses column information in tests and those tests break
      if tests are run in random order.
      09beb9c2
  3. 26 7月, 2013 1 次提交
  4. 25 7月, 2013 4 次提交
  5. 24 7月, 2013 2 次提交
  6. 23 7月, 2013 1 次提交
  7. 22 7月, 2013 4 次提交
    • B
      Don't allow `quote_value` to be called without a column · 31a43ebc
      Ben Woosley 提交于
      Some adapters require column information to do their job properly.
      By enforcing the provision of the column for this internal method
      we ensure that those using adapters that require column information
      will always get the proper behavior.
      31a43ebc
    • B
      Tidy up the "Specified column type for quote_value" changes · c083dc22
      Ben Woosley 提交于
      This includes fixing typos in changelog, removing a deprecated
      mocha/setup test require, and preferring the `column_for_attribute`
      accessor over direct access to the columns_hash in the new code.
      c083dc22
    • A
      Specified column type for quote_value · 39b5bfe2
      Alfred Wong 提交于
      When calling quote_value the underlying connection sometimes requires
      more information about the column to properly return the correct quoted
      value.
      
      I ran into this issue when using optimistic locking in JRuby and the
      activerecord-jdbcmssql-adapter. In SQLSever 2000, we aren't allowed to
      insert a integer into a NVARCHAR column type so we need to format it as
      N'3' if we want to insert into the NVARCHAR type. Unfortuantely, without
      the column type being passed the connection adapter cannot properly return
      the correct quote value because it doesn't know to return N'3' or '3'.
      
      This patch is fairly straight forward where it just passes in the column
      type into the quote_value, as it already has the ability to take in the column,
      so it can properly handle at the connection level.
      
      I've added the tests required to make sure that the quote_value method
      is being passed the column type so that the underlying connection can
      determine how to quote the value.
      39b5bfe2
    • V
      rescue from all exceptions in `ConnectionManagement#call` · 0b6c1f08
      Vipul A M 提交于
      Fixes #11497
      
      As `ActiveRecord::ConnectionAdapters::ConnectionManagement` middleware does not rescue from Exception (but only from StandardError),
      the Connection Pool quickly runs out of connections when multiple erroneous Requests come in right after each other.
      
      Recueing from all exceptions and not just StandardError, fixes this behaviour.
      0b6c1f08
  8. 17 7月, 2013 1 次提交
  9. 16 7月, 2013 7 次提交
  10. 15 7月, 2013 2 次提交
    • E
      Blacklist->whitelist for reference scans in order! · e2d82508
      Ernie Miller 提交于
      Stop special-casing Arel::Nodes as exempt from reference scanning in
      order. Instead, only scan order values that are strings for a table
      reference.
      e2d82508
    • P
      #4566: Remove extra decrement of transaction level · e0d59e62
      Paul Nikitochkin 提交于
      `rollback_active_record_state!` tries to restore model state on `Exception`
      by invoking `restore_transaction_record_state` it decrement deep level by `1`.
      
      After restoring it ensure that states to be cleared
      and level decremented by invoking `clear_transaction_record_state`,
      which cause the bug: because state already reduced in `restore_transaction_record_state`.
      
      Removed double derement of transaction level
      and removed duplicated code which clear transaction state for top level.
      e0d59e62
  11. 14 7月, 2013 1 次提交
  12. 09 7月, 2013 7 次提交
  13. 07 7月, 2013 1 次提交
  14. 05 7月, 2013 4 次提交
  15. 04 7月, 2013 3 次提交