- 23 6月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
This is public API, and `simple_form` depends on the `nil` return value. We need to go through a deprecation cycle to return a null object. If people want hash access, they can access the hash.
-
由 Yves Senn 提交于
/cc @sgrif
-
- 18 6月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
-
由 Sean Griffin 提交于
If the through record gets created in an `after_create` hook that is defined before the association is defined (therefore after its `after_create` hook) get saved twice. This ensures that the through records are created only once, regardless of the order of the hooks.
-
- 17 6月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 14 6月, 2014 5 次提交
-
-
由 Sean Griffin 提交于
We've stopped using it internally, in favor of polymorphism. So should you!
-
由 Akshay Vishnoi 提交于
-
由 Matthew Draper 提交于
Fixes #15705.
-
由 Sean Griffin 提交于
member = Member.new(club: Club.new) member.save! Before: member.current_membership.club_id # => nil After: member.current_membership.club_id # => club's id
-
由 Sean Griffin 提交于
We have several mutable types on Active Record now. (Serialized, JSON, HStore). We need to be able to detect if these have been modified in place.
-
- 12 6月, 2014 2 次提交
-
-
由 Wojciech Wnętrzak 提交于
Additionally: * It changes `purge` task on `sqlite3` adapter to recreate database file, to be consistent with other adapters. * Adds `purge` step when loading from `schema.rb`
-
由 Sean Griffin 提交于
The column name given by the adapter doesn't include the table namespace, so going through the hashed version of the result set causes overridden keys. Fixes #15649
-
- 11 6月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
The original patch that added this concept can be found [here](https://web.archive.org/web/20090601022739/http://dev.rubyonrails.org/ticket/9767). The current default behavior is to cache everything except serialized columns, unless the user specified otherwise. If anyone were to specify otherwise, many types would actually be completely broken. Still, the method is left in place with a deprecation warning in case anyone is actually still calling this method.
-
由 Akshay Vishnoi 提交于
-
- 10 6月, 2014 2 次提交
-
-
由 James Yang 提交于
-
由 Rafael Mendonça França 提交于
This reverts commit dd3ea171 and add a regression test. Fixes #15418
-
- 07 6月, 2014 1 次提交
-
-
由 Yves Senn 提交于
This is a follow up to #15556 @kuldeepaggarwal did submit this patch way back (#13624).
-
- 06 6月, 2014 3 次提交
-
-
由 Yves Senn 提交于
[ci skip]
-
由 Yves Senn 提交于
Before this patch, using `ActiveRecord::Base.primary_key_prefix_type` with `:table_name_with_underscore` would change the `SchemaMigration` model to have a primary key. This resulted in broken queries for PG because it tried to return the inserted PK (which does not exist). Closes #15051. Closes #15419.
-
由 Yves Senn 提交于
The migration numbers were normalized different ways. This left the task output in an inconsistent state. Closes #15538.
-
- 05 6月, 2014 1 次提交
-
-
由 Akshay Vishnoi 提交于
-
- 04 6月, 2014 2 次提交
-
-
由 Godfrey Chan 提交于
-
由 Lauro Caetano 提交于
than existing column. Fixes #15480.
-
- 03 6月, 2014 4 次提交
-
-
由 Yves Senn 提交于
-
由 Sean Griffin 提交于
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
-
- 02 6月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
-
- 30 5月, 2014 3 次提交
- 29 5月, 2014 1 次提交
-
-
由 Ethan 提交于
-
- 28 5月, 2014 3 次提交
-
-
由 Yves Senn 提交于
The solution presented in this patch is not efficient. We should replace it in the near future. The following needs to be worked out: * Is `@attributes` storing the Ruby or SQL representation? * `cacheable_column?` is broken but `hstore` and `json` rely on that behavior Refs #15369. /cc @sgrif @rafaelfranca
-
由 Sean Griffin 提交于
Making this part of the public API was premature, let's make it private again while I continue to work on the surrounding code.
-
由 Rafael Mendonça França 提交于
-
- 27 5月, 2014 3 次提交
-
-
由 Arthur Neves 提交于
After ad7b5efb, which changed how has_an_belongs_to_many used to work, we start raising an error when redefining the same has_an_belongs_to_many association. This commits fix that regression. [Fixes #14983]
-
由 Zachary Scott 提交于
-
由 Sean Griffin 提交于
As a result of all of the refactoring that's been done, it's now possible for us to define a public API to allow users to specify behavior. This is an initial implementation so that I can work off of it in smaller pieces for additional features/refactorings. The current behavior will continue to stay the same, though I'd like to refactor towards the automatic schema detection being built off of this API, and add the ability to opt out of automatic schema detection. Use cases: - We can deprecate a lot of the edge cases around types, now that there is an alternate path for users who wish to maintain the same behavior. - I intend to refactor serialized columns to be built on top of this API. - Gem and library maintainers are able to interact with `ActiveRecord` at a slightly lower level in a more stable way. - Interesting ability to reverse the work flow of adding to the schema. Model can become the single source of truth for the structure. We can compare that to what the database says the schema is, diff them, and generate a migration.
-
- 25 5月, 2014 1 次提交
-
-
由 Arthur Neves 提交于
Fix habtm reflection Conflicts: activerecord/CHANGELOG.md activerecord/lib/active_record/counter_cache.rb activerecord/lib/active_record/reflection.rb activerecord/test/cases/reflection_test.rb
-
- 24 5月, 2014 1 次提交
-
-
由 Zachary Scott 提交于
-