- 14 11月, 2014 1 次提交
-
-
由 Arun Agrawal 提交于
`Computer` class needs to be require See #17217 for more details
-
- 01 11月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
Fixes #17170
-
由 Sean Griffin 提交于
Sufficiently large integers cause `find` and `find_by` to raise `StatementInvalid` instead of `RecordNotFound` or just returning `nil`. Given that we can't cast to `nil` for `Integer` like we would with junk data for other types, we raise a `RangeError` instead, and rescue in places where it would be highly unexpected to get an exception from casting. Fixes #17380
-
- 02 9月, 2014 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 29 8月, 2014 3 次提交
-
-
由 Akira Matsuda 提交于
-
由 Akira Matsuda 提交于
-
由 Akira Matsuda 提交于
-
- 20 8月, 2014 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 14 8月, 2014 1 次提交
-
-
由 Jeremy McNevin 提交于
This method would assume that if last migration in the migrations directory matched the current schema version, that the database was up to date, but this does not account for new migrations with older timestamps that may be pending.
-
- 13 8月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
As per discussion, this changes the model generators to specify `null: false` for timestamp columns. A warning is now emitted if `timestamps` is called without a `null` option specified, so we can safely change the behavior when no option is specified in Rails 5.
-
- 22 7月, 2014 2 次提交
-
-
由 Yves Senn 提交于
The fixtures are still in play, adding a new column without a default and `null: true` is not possible. This reverts back to leaking global state, as our `schema.rb` adds the `null: false` constraint on this field. A future solution would be to make the `migration_test.rb` run independent of fixture tables. This way we can simply drop the state after test execution, without worrying about side effects. /cc @zuhao
-
由 Zuhao Wan 提交于
-
- 16 7月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 18 6月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
If we want to have type decorators mess with the attribute, but not the column, we need to stop type casting on the column. Where possible, we changed the tests to test the value of `column_defaults`, which is public API. `Column#default` is not.
-
- 07 6月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
For consistency with https://github.com/rails/rails/pull/15557
-
- 05 6月, 2014 1 次提交
-
-
由 Akshay Vishnoi 提交于
-
- 28 5月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Missed a case that only occured for mysql/mysql2
-
- 27 5月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
With ActiveRecord::Properties, we now have a reasonable path for users to continue to keep this behavior if they want it. This is an edge case that has added a lot of complexity to the code base.
-
- 15 3月, 2014 1 次提交
-
-
由 Guo Xiang Tan 提交于
Follow-Up to https://github.com/rails/rails/pull/14348 Ensure that SQLCounter.clear_log is called after each test. This is a step to prevent side effects when running tests. This will allow us to run them in random order.
-
- 16 1月, 2014 2 次提交
- 06 1月, 2014 1 次提交
-
-
由 Dylan Thacker-Smith 提交于
-
- 14 12月, 2013 1 次提交
-
-
由 Cody Cutrer 提交于
also override drop_table in AbstractMySQLAdapter to properly drop temporary tables without committing the transaction
-
- 12 12月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
We can now make use of the existent #travel/#travel_to helper methods added to AS test case and available in all tests.
-
- 16 11月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 09 11月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 08 11月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
We can conditional define the tests depending on the adapter or connection. Lets keep the skip for fail tests that need to be fixed.
-
- 01 11月, 2013 1 次提交
-
-
由 Arun Agrawal 提交于
Same as 4d4ff531
-
- 27 10月, 2013 1 次提交
-
-
由 Jerad Phelps 提交于
added schema_migrations_table_name to ActiveRecord::Base in order that the name of the schema migrations table can be configured. consolidated test_schema_migrations_table_name tests Added changelog entry edited changelog removed commented lines removed reader ensure the schema migrations table is reset at end of test added entry to configuration guide guides typo and changelog order
-
- 25 8月, 2013 1 次提交
-
-
由 wangjohn 提交于
This prevents deprecation warnings from popping up.
-
- 23 8月, 2013 1 次提交
-
-
由 wangjohn 提交于
The options will specify the prefix and the suffix. Also, I'm moving the method to be an instance method on the +Migration+ instance. This makes more sense than being a class method on the +Migrator+ class because the only place that uses it is on a +Migration+ instance (in a method_missing hook). The logic for the Migrator shouldn't be doing any work to calculate the table name, it should be the Migration itself. Also made some small indentation fixes.
-
- 29 7月, 2013 1 次提交
-
-
由 Akira Matsuda 提交于
This reverts commit 10259c3e. reason: this causes rake test_mysql and test_mysql2 fail
-
- 28 7月, 2013 1 次提交
-
-
由 Neeraj Singh 提交于
If the order in which tests are executed is changed then test fails. This commit ensures that all migrations are run before ensuring that there are no pending migration.
-
- 16 7月, 2013 1 次提交
-
-
由 Xavier Noria 提交于
-
- 05 6月, 2013 1 次提交
-
-
由 kennyj 提交于
-
- 19 4月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 18 4月, 2013 1 次提交
-
-
由 bondarev 提交于
-
- 09 3月, 2013 1 次提交
-
-
由 OZAWA Sakuro 提交于
During insertion of "# This migration comes from ... " comment at the beginning of a migration, presence of magic comment was not considered.
-
- 08 3月, 2013 1 次提交
-
-
由 Ezekiel Smithburg 提交于
schema_statements uses the column name by default to construct the index name, and then raises an exception if it doesn't exist, even if the name option is specified, which causes #8858. this commit makes index_name_for_remove fall back to constructing the index name to remove based on the name option.
-
- 05 3月, 2013 1 次提交
-
-
由 Yves Senn 提交于
Closes #9483. There are SQL Queries that can't run inside a transaction. Since the Migrator used to wrap all Migrations inside a transaction there was no way to run these queries within a migration. This patch adds `self.disable_ddl_transaction!` to the migration to turn transactions off when necessary.
-