aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge pull request #15290 from sgrif/sg-consolidate-zero-scale-decimalRafael Mendonça França2014-05-231-6/+10
|\ \ \ | | | | | | | | Remove special case in schema dumper for decimal without scale
| * | | Remove special case in schema dumper for decimal without scaleSean Griffin2014-05-231-6/+10
| | | |
* | | | Remove duplicated parameter check on #where!Sergey Alekseev2014-05-231-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems that #where! is not designed to be used as a chained where. See initial implementation at 8c2c60511beaad05a218e73c4918ab89fb1804f0. So, no need to check twice. We should not test #where! https://github.com/rails/rails/pull/15285#discussion_r13018316
* | | Merge pull request #15282 from sgrif/sg-remove-column-primaryRafael Mendonça França2014-05-234-40/+5
|\ \ \ | | | | | | | | Remove `Column#primary`
| * | | Remove `Column#primary`Sean Griffin2014-05-234-40/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It appears to have been used at some point in the past, but is no longer used in any meaningful way. Whether a column is considered primary is a property of the model, not the schema/column. This also removes the need for yet another layer of caching of the model's schema, and we can leave that to the schema cache.
* | | | Merge pull request #15271 from sgrif/sg-remove-duplicated-setupRafael Mendonça França2014-05-231-4/+3
|\ \ \ \ | | | | | | | | | | Remove duplicated setup in test
| * | | | Remove duplicated setup in testSean Griffin2014-05-231-4/+3
| |/ / /
* | | | Merge pull request #15274 from sgrif/sg-move-type-testsRafael Mendonça França2014-05-232-159/+159
|\ \ \ \ | | | | | | | | | | Change typecasting unit tests to test type objects directly
| * | | | Change typecasting unit tests to test type objects directlySean Griffin2014-05-232-159/+159
| |/ / / | | | | | | | | | | | | | | | | | | | | There's no longer type casting behavior of any kind inside of `Column` for the general case. These tests can be made clearer by testing the type objects directly.
* | | | Fixed serialization for records with an attribute named `format`.Godfrey Chan2014-05-221-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * * * This bug can be triggered when serializing record R (the instance) of type C (the class), provided that the following conditions are met: 1. The name of one or more columns/attributes on C/R matches an existing private method on C (e.g. those defined by `Kernel`, such as `format`). 2. The attribute methods have not yet been generated on C. In this case, the matching private methods will be called by the serialization code (with no arguments) and their return values will be serialized instead. If the method requires one or more arguments, it will result in an `ArgumentError`. This regression is introduced in d1316bb. * * * Attribute methods (e.g. `#name` and `#format`, assuming the class has columns named `name` and `format` in its database table) are lazily defined. Instead of defining them when a the class is defined (e.g. in the `inherited` hook on `ActiveRecord::Base`), this operation is deferred until they are first accessed. The reason behind this is that is defining those methods requires knowing what columns are defined on the database table, which usually requires a round-trip to the database. Deferring their definition until the last-possible moment helps reducing unnessary work, especially in development mode where classes are redefined and throw away between requests. Typically, when an attribute is first accessed (e.g. `a_book.format`), it will fire the `method_missing` hook on the class, which triggers the definition of the attribute methods. This even works for methods like `format`, because calling a private method with an explicit receiver will also trigger that hook. Unfortunately, `read_attribute_for_serialization` is simply an alias to `send`, which does not respect method visibility. As a result, when serializing a record with those conflicting attributes, the `method_missing` is not fired, and as a result the attribute methods are not defined one would expected. Before d1316bb, this is negated by the fact that calling the `run_callbacks` method will also trigger a call to `respond_to?`, which is another trigger point for the class to define its attribute methods. Therefore, when Active Record tries to run the `after_find` callbacks, it will also define all the attribute methods thus masking the problem. * * * The proper fix for this problem is probably to restrict `read_attribute_for_serialization` to call public methods only (i.e. alias `read_attribute_for_serialization` to `public_send` instead of `send`). This however would be quite risky to change in a patch release and would probably require a full deprecation cycle. Another approach would be to override `read_attribute_for_serialization` inside Active Record to force the definition of attribute methods: def read_attribute_for_serialization(attribute) self.class.define_attribute_methods send(attribute) end Unfortunately, this is quite likely going to cause a performance degradation. This patch therefore restores the behaviour from the 4-0-stable branch by explicitly forcing the class to define its attribute methods in a similar spot (when records are initialized). This should not cause any extra roundtrips to the database because the `@columns` should already be cached on the class. Fixes #15188.
* | | | Don't recurse infinitely when calling non-existent method on superKris Kemper2014-05-221-0/+12
|/ / /
* | | Push limit to type objectsSean Griffin2014-05-221-3/+3
| | | | | | | | | | | | | | | Columns and injected types no longer have any conditionals based on the format of SQL type strings! Hooray!
* | | Merge pull request #15249 from sgrif/sg-register-types-in-adapterRafael Mendonça França2014-05-221-9/+1
|\ \ \ | | | | | | | | Use the generic type map for all PG type registrations
| * | | Use the generic type map for all PG type registrationsSean Griffin2014-05-221-9/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We're going to want all of the benefits of the type map object for registrations, including block registration and real aliasing. Moves type name registrations to the adapter, and aliases the OIDs to the named types
* | | | Merge pull request #15248 from sgrif/sg-additional-type-map-argsRafael Mendonça França2014-05-221-0/+17
|\ \ \ \ | | | | | | | | | | Allow additional arguments to be used during type map lookups
| * | | | Allow additional arguments to be used during type map lookupsSean Griffin2014-05-221-0/+17
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Determining things like precision and scale in postgresql will require the given blocks to take additional arguments besides the OID. - Adds the ability to handle additional arguments to `TypeMap` - Passes the column type to blocks when looking up PG types
* | | | pg test, extract tsvector tests into `postgresql/full_text_test.rb`Yves Senn2014-05-222-27/+31
| | | |
* | | | pg test, move timestamp tests over to `postgresql/timestamp_test.rb`.Yves Senn2014-05-222-43/+53
| | | |
* | | | pg test, extract network address type tests into separate file.Yves Senn2014-05-223-51/+79
| | | |
* | | | pg test, remove unused code.Yves Senn2014-05-221-3/+0
|/ / /
* | | Merge pull request #14803 from kuldeepaggarwal/null_relation_sum_fixMatthew Draper2014-05-221-0/+44
|\ \ \ | | | | | | | | | | | | Fixed a problem where `sum` used with a `group` was not returning a Hash.
| * | | Fixed a problem where `sum`, `size`, `average`, `minimum` and `maximum` usedKuldeep Aggarwal2014-05-151-0/+44
| | | | | | | | | | | | | | | | with a grouping was not returning a Hash.
* | | | Merge pull request #15237 from sgrif/sg-move-extract-scaleRafael Mendonça França2014-05-211-2/+2
|\ \ \ \ | | | | | | | | | | Move extract_scale to decimal type
| * | | | Move extract_scale to decimal typeSean Griffin2014-05-211-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The only type that has a scale is decimal. There's a special case where decimal columns with 0 scale are type cast to integers if the scale is not specified. Appears to only affect schema dumping.
* | | | | Rename `oid_type` to `cast_type` to make PG columns consistentSean Griffin2014-05-211-10/+1
|/ / / /
* | | | Merge pull request #14613 from Sirupsen/fix-serialize-update-columnRafael Mendonça França2014-05-211-0/+16
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix serialized field returning serialized data after update_column Conflicts: activerecord/CHANGELOG.md
| * | | | Fix serialized field returning serialized data after update_columnSimon Eskildsen2014-04-051-0/+16
| | | | |
* | | | | Revert "Merge pull request #14544 from jefflai2/named_scope_sti"Rafael Mendonça França2014-05-211-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 9a1abedcdeecd9464668695d4f9c1d55a2fd9332, reversing changes made to c72d6c91a7c0c2dc81cc857a1d6db496e84e0065. Conflicts: activerecord/CHANGELOG.md activerecord/test/models/comment.rb This change break integration with activerecord-deprecated_finders so I'm reverting until we find a way to make it work with this gem.
* | | | | pg, extract money tests into separate file.Yves Senn2014-05-212-35/+55
| | | | | | | | | | | | | | | | | | | | | | | | | - Added assertions about the column. Specifically scale. - Move record insertion from setup into test method.
* | | | | Fix polymorphic eager load with foreign_key as String.Lauro Caetano2014-05-201-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The foreign_key could be `String` and just doing `owners_map[owner_key]` could return `nil`. To prevent this bug, we should `to_s` both keys if their types are different. Fixes #14734.
* | | | | Merge pull request #14544 from jefflai2/named_scope_stiRafael Mendonça França2014-05-201-1/+6
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes Issue #13466. Conflicts: activerecord/CHANGELOG.md
| * | | | | Fixes Issue #13466.Jefferson Lai2014-04-231-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changed the call to a scope block to be evaluated with instance_eval. The result is that ScopeRegistry can use the actual class instead of base_class when caching scopes so queries made by classes with a common ancestor won't leak scopes.
* | | | | | Merge pull request #14979 from brocktimus/masterRafael Mendonça França2014-05-201-0/+7
|\ \ \ \ \ \ | | | | | | | | | | | | | | Making belongs_to: touch behaviour be consistent with save updating updated_at
| * | | | | | Prevented belongs_to: touch propagating up if there are no changes being savedBrock Trappitt2014-05-211-0/+7
| | | | | | |
* | | | | | | Revert "Revert "Merge pull request #8313 from ↵Rafael Mendonça França2014-05-201-0/+13
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | alan/only_save_changed_has_one_objects"" This reverts commit e94e6c27af495a2460c811bb506459f1428dec6b. Conflicts: activerecord/CHANGELOG.md The original commit was reverted only to be safe since #14407 were reported. We don't have any proof we added a regression with the original commit so reverting it now will give us more problem. Closes #14407
* | | | | | Merge pull request #15207 from sgrif/sg-inline-column-helpersRafael Mendonça França2014-05-201-1/+2
|\ \ \ \ \ \ | | | | | | | | | | | | | | Inline typecasting helpers from Column to the appropriate types
| * | | | | | Inline typecasting helpers from Column to the appropriate typesSean Griffin2014-05-201-1/+2
| | | | | | |
* | | | | | | Delegate predicate methods to injected type object on ColumnSean Griffin2014-05-201-1/+1
|/ / / / / /
* | | | | | Use the generic type map object for mysql field lookupsSean Griffin2014-05-201-0/+13
| | | | | |
* | | | | | Merge pull request #15203 from sgrif/sg-delegate-type-castRafael Mendonça França2014-05-201-1/+1
|\ \ \ \ \ \ | | | | | | | | | | | | | | Replace `type_cast` case statement with delegation
| * | | | | | Replace `type_cast` case statement with delegationSean Griffin2014-05-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All subclasses of column were now delegating `type_cast` to their injected type object. We can remove the overriding methods, and generalize it on the `Column` class itself. This also enabled us to remove several column classes completely, as they no longer had any meaningful behavior of their own.
* | | | | | | Merge pull request #15201 from sgrif/sg-types-postgresqlRafael Mendonça França2014-05-201-4/+4
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | Have Postgres OID types inherit from general types
| * | | | | | | Have Postgres OID types inherit from general typesSean Griffin2014-05-201-4/+4
| |/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using general types where possible. Several more can go away once infinity gets figured out.
* / / / / / / fix multiple hash preloads. Fixes #14994Aaron Patterson2014-05-201-0/+7
|/ / / / / /
* | | | | | Merge pull request #15197 from sgrif/sg-delegate-type-cast-sqlite3Yves Senn2014-05-201-1/+1
|\ \ \ \ \ \ | | | | | | | | | | | | | | Delegate `#type_cast` to injected type objects on SQLite3
| * | | | | | Delegate `#type_cast` to injected type objects on SQLite3Sean Griffin2014-05-201-1/+1
| | | | | | |
* | | | | | | Fixed the inferred table name for HABTM within a schemaEric Chahin2014-05-201-0/+26
|/ / / / / / | | | | | | | | | | | | | | | | | | Fixes #14824.
* | | | | | fix `rake test_sqlite3_mem`.Yves Senn2014-05-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While running Sqlite3 memory tests I encountered the following error: ``` Finished in 69.416366s, 58.0267 runs/s, 162.3681 assertions/s. 1) Error: ActiveRecord::Migration::ChangeSchemaTest#test_add_column_with_timestamp_type: NoMethodError: undefined method `type' for nil:NilClass /Users/senny/Projects/rails/activerecord/test/cases/migration/change_schema_test.rb:244:in `test_add_column_with_timestamp_type' 4028 runs, 11271 assertions, 0 failures, 1 errors, 1 skips ``` This was because the table `testings` was used in multiple test-cases. This resulted in a wrongly cached schema on `ActiveRecord::Base.schema_chae`. /cc @zuhao
* | | | | | docs, `instantiate` expects `String` keys. [Rafal Piekarski & Yves Senn]Yves Senn2014-05-201-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #15122 Closes #15107
* | | | | | Remove :timestamp column typeSean Griffin2014-05-195-21/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `:timestamp` type for columns is unused. All database adapters treat them as the same database type. All code in `ActiveRecord` which changes its behavior based on the column's type acts the same in both cases. However, when the type is passed to code that checks for the `:datetime` type, but not `:timestamp` (such as XML serialization), the result is unexpected behavior. Existing schema definitions will continue to work, and the `timestamp` type is transparently aliased to `datetime`.