- 07 5月, 2017 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 11 12月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
It is enough to distinguish only the trailing `unsigned` and `unsigned zerofill`.
-
- 06 12月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Raise `ActiveRecord::RangeError` when values that executed are out of range.
-
- 27 11月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Fixes #27125.
-
- 26 10月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Follow up to 99cf7558.
-
- 04 5月, 2016 1 次提交
-
-
由 Vipul A M 提交于
Fix failing tests
-
- 11 3月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Before: ```ruby create_table "big_numbers", force: :cascade do |t| t.integer "bigint_column", limit: 8 end ``` After: ```ruby create_table "big_numbers", force: :cascade do |t| t.bigint "bigint_column" end ```
-
- 18 12月, 2015 1 次提交
-
-
由 Matthew Draper 提交于
-
- 18 9月, 2015 2 次提交
-
-
由 Ryuta Kamizono 提交于
In the case of using `unsigned` as the type: create_table :foos do |t| t.unsigned_integer :unsigned_integer t.unsigned_bigint :unsigned_bigint t.unsigned_float :unsigned_float t.unsigned_decimal :unsigned_decimal, precision: 10, scale: 2 end
-
由 Ryuta Kamizono 提交于
Example: create_table :foos do |t| t.integer :unsigned_integer, unsigned: true t.bigint :unsigned_bigint, unsigned: true t.float :unsigned_float, unsigned: true t.decimal :unsigned_decimal, unsigned: true, precision: 10, scale: 2 end
-
- 11 6月, 2015 1 次提交
-
-
由 Yves Senn 提交于
-
- 17 3月, 2015 1 次提交
-
-
由 Brandon Weiss 提交于
I’m renaming all instances of `use_transcational_fixtures` to `use_transactional_tests` and “transactional fixtures” to “transactional tests”. I’m deprecating `use_transactional_fixtures=`. So anyone who is explicitly setting this will get a warning telling them to use `use_transactional_tests=` instead. I’m maintaining backwards compatibility—both forms will work. `use_transactional_tests` will check to see if `use_transactional_fixtures` is set and use that, otherwise it will use itself. But because `use_transactional_tests` is a class attribute (created with `class_attribute`) this requires a little bit of hoop jumping. The writer method that `class_attribute` generates defines a new reader method that return the value being set. Which means we can’t set the default of `true` using `use_transactional_tests=` as was done previously because that won’t take into account anyone using `use_transactional_fixtures`. Instead I defined the reader method manually and it checks `use_transactional_fixtures`. If it was set then it should be used, otherwise it should return the default, which is `true`. If someone uses `use_transactional_tests=` then it will overwrite the backwards-compatible method with whatever they set.
-
- 11 12月, 2014 1 次提交
-
-
由 Ryuta Kamizono 提交于
-