- 23 12月, 2013 9 次提交
-
-
由 Yves Senn 提交于
On destroying do not touch destroyed belongs to association.
-
由 Paul Nikitochkin 提交于
Fixes: #13445
-
由 Yves Senn 提交于
Resolver test cases
-
由 Kuldeep Aggarwal 提交于
-
由 José Valim 提交于
Add missing av/railtie require
-
由 Łukasz Strzałkowski 提交于
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
Fix typecasting array of integers
-
由 Damien Mathieu 提交于
Closes #13444
-
- 22 12月, 2013 10 次提交
-
-
由 Godfrey Chan 提交于
-
由 Andrew White 提交于
-
由 Guillermo Iguaran 提交于
Fix DB Console tests
-
由 schneems 提交于
-
由 schneems 提交于
The build is broken: https://travis-ci.org/rails/rails/builds/15824530 This commit fixes it. The problem: Sqlite expects the `database` part to be an absolute path. That prompted this change to be committed to master: https://github.com/rails/rails/commit/fbb79b517f3127ba620fedd01849f9628b78d6ce This change provides correct behavior. Unfortunately tests were introduced in https://github.com/rails/rails/commit/971d5107cd4cd08c22a85d34546f4ba03ed5c925 that were relying on the incorrect behavior. We can avoid the fix by changing to another database url such as `mysql` or `postgresql` In addition to fixing the failure, the assertions are changed so that the "expected" value comes before "actual" value.
-
由 Guillermo Iguaran 提交于
Enable memcached service on travis for running cache tests.
-
由 Guillermo Iguaran 提交于
Add missing changelog entries and fix few typos
-
由 Vipul A M 提交于
-
由 Robin Dupret 提交于
-
由 Carlos Antonio da Silva 提交于
-
- 21 12月, 2013 9 次提交
-
-
由 Robin Dupret 提交于
-
由 Xavier Noria 提交于
-
由 Robin Dupret 提交于
-
由 Xavier Noria 提交于
AC::Parameters#fetch was refactored in 7171111d to prevent self mutation, but in doing so it hardcodes logic #convert_hashes_to_parameters is supposed to encapsulate. Better leave the delegation, and add a way to avoid mutating self in there.
-
由 Guillermo Iguaran 提交于
-
由 David Heinemeier Hansson 提交于
Generates html and text templates for mailers by default.
-
由 Xavier Noria 提交于
-
由 Aaron Patterson 提交于
-
由 Kassio Borges 提交于
-
- 20 12月, 2013 12 次提交
-
-
由 Rafael Mendonça França 提交于
Bump Jbuilder version to 2.0.0
-
由 Pavel Pravosud 提交于
-
由 Yves Senn 提交于
Do not expect database user with app name to exist
-
before: ActiveSupport::NumberHelper.number_to_rounded '3.14159', precision: 50 => "3.14158999999999988261834005243144929409027099609375" after: ActiveSupport::NumberHelper.number_to_rounded '3.14159', precision: 50 => "3.14159000000000000000000000000000000000000000000000"
-
由 Jeremy Kemper 提交于
Add configuration option to optionally disable deep_munge Conflicts: actionpack/CHANGELOG.md
-
由 Guillermo Iguaran 提交于
Use sass-rails 4.0.0
-
由 Takayuki Matsubara 提交于
-
由 Richard Schneeman 提交于
fix CollectionAssociation's comments
-
由 schneems 提交于
By default when creating a project with `--database=postgresql` the `config/database.yml` file that is generated has a user specified that is the same as the app name ``` development: adapter: postgresql encoding: unicode database: <%= app_name %>_development pool: 5 username: <%= app_name %> password: ``` This is counterintuitive and would rarely be valid. By default postgres creates a user with the current user name (http://www.postgresql.org/docs/9.3/static/database-roles.html) "it will have the same name as the operating system user that initialized the database cluster": ``` $ whoami schneems ``` If the `username` is left out postgresql will assume that you wish to log in as the default user ``` $ psql -c '\du' List of roles Role name | Attributes | Member of -----------+------------------------------------------------+----------- schneems | Superuser, Create role, Create DB, Replication | {} ``` A good sensible default then for auto generated `database.yml` files is to remove the `username`, and have postgres attempt to connect to the database as the currently logged in user. Instead of submitting with a blank password, don't submit a password.
-
由 Ben Angel 提交于
change CollectionAssociation's comments to say Association instead of AssociationProxy to match changes for 3.1 removing Association proxy.
-
由 Guillermo Iguaran 提交于
Flag `config.assets.raise_runtime_errors` in dev
-
由 schneems 提交于
By default `config.assets.raise_runtime_errors` should be set to `true` in development for new apps. Source: https://github.com/rails/sprockets-rails/pull/100
-