aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib
Commit message (Collapse)AuthorAgeFilesLines
* docs, `instantiate` expects `String` keys. [Rafal Piekarski & Yves Senn]Yves Senn2014-05-201-4/+4
| | | | | Closes #15122 Closes #15107
* Remove :timestamp column typeSean Griffin2014-05-1912-26/+16
| | | | | | | | | | | | 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`.
* Merge pull request #10798 from ↵Rafael Mendonça França2014-05-191-1/+1
|\ | | | | | | | | | | | | | | | | | | jcxplorer/fix-enable_extension-with-table_name_prefix Fix migrations that use enable_extension with table_name_prefix/suffix Conflicts: activerecord/CHANGELOG.md activerecord/lib/active_record/migration.rb
| * Fix migrations with enable_extensionJoao Carlos2013-05-291-1/+1
| | | | | | | | | | | | | | When using ActiveRecord::Base.table_name_prefix and/or table_name_suffix, extension names got the same treatment as table names when running migrations. This led to migrations that tried to call, for example, enable_extension("prefix_hstore") on the connection.
* | Delegate `Column#type` to the injected type objectSean Griffin2014-05-1921-71/+258
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The decision to wrap type registrations in a proc was made for two reasons. 1. Some cases need to make an additional decision based on the type (e.g. a `Decimal` with a 0 scale) 2. Aliased types are automatically updated if they type they point to is updated later. If a user or another adapter decides to change the object used for `decimal` columns, `numeric`, and `number` will automatically point to the new type, without having to track what types are aliased explicitly. Everything else here should be pretty straightforward. PostgreSQL ranges had to change slightly, since the `simplified_type` method is gone.
* | Merge pull request #15168 from ↵Rafael Mendonça França2014-05-191-0/+2
|\ \ | | | | | | | | | | | | eileencodes/return-early-on-delete-and-destroy-methods Return early on delete and destroy methods
| * | early return on delete and destroy methodseileencodes2014-05-181-0/+2
| | | | | | | | | | | | | | | | | | When delete or destroy is called on all records nothing is deleted or destroyed. Intead of running through the code and still not deleteing anything, we should early return
* | | Merge pull request #14126 from schuetzm/index_option_for_columnRafael Mendonça França2014-05-191-6/+13
|\ \ \ | | | | | | | | Make `:index` in migrations work with all column types
| * | | Make `:index` in migrations work with all column typesMarc Schütz2014-05-181-6/+13
| |/ /
* | | Merge pull request #15160 from sgrif/sg-destructured-eachRafael Mendonça França2014-05-191-4/+4
|\ \ \ | | | | | | | | Use destructured arguments when looping through pairs
| * | | Use destructured arguments when looping through pairsSean Griffin2014-05-171-4/+4
| | | | | | | | | | | | | | | | Minor refactoring of looping behavior for aggregation
* | | | pg, re-introduce `PostgreSQL::Utils` to unify schema/table extraction.Yves Senn2014-05-194-24/+31
| | | | | | | | | | | | | | | | Partial revert of c0bfc3f412834ffe8327a15ae3a46602cc28e425
* | | | pg, add missing nodocs for extracted modules.Yves Senn2014-05-195-10/+10
| | | |
* | | | Merge pull request #15156 from sgrif/sg-postgres-timestampsYves Senn2014-05-181-6/+3
|\ \ \ \ | |_|/ / |/| | | PostgreSQL timestamps should always be datetimes
| * | | PostgreSQL timestamps are always datetimesSean Griffin2014-05-171-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current behavior is that they are treated as `datetime` normally, but if they are part of an array, they are treated as `timestamp`. The only place that seems to be impacted by this is schema dumping, which shouldn't matter since `t.datetime` and `t.timestamp` are equivalent in the `PostgreSQL` adapter, anyway.
* | | | Add a type object to Column constructorSean Griffin2014-05-179-12/+40
| |/ / |/| | | | | | | | | | | | | | Part of #15134. In order to perform typecasting polymorphically, we need to add another argument to the constructor. The order was chosen to match the `oid_type` on `PostgreSQLColumn`.
* | | Remove dead test code for unsupported adaptersSean Griffin2014-05-173-11/+2
|/ /
* | Merge pull request #14428 from jnormore/reset_counters_aliasRafael Mendonça França2014-05-171-5/+10
|\ \ | | | | | | Updates reset_counters to allow counter name in params
| * | Updates reset_counters to allow counter name in paramsJason Normore2014-05-161-5/+10
| | | | | | | | | | | | | | | | | | | | | Add support for counter name to be passed as parameter on `CounterCache::ClassMethods#reset_counters`. This is to be consistent with the other methods in the module that all accept counter name.
* | | fix typo [ci skip]Vijay Dev2014-05-171-1/+1
|/ /
* | Merge pull request #15071 from leafac/issues/11985Rafael Mendonça França2014-05-161-3/+13
|\ \ | | | | | | Fix `Relation#delete_all` inconsistency
| * | Fix `Relation#delete_all` inconsistencyLeandro Facchinetti2014-05-161-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | When relation scopes include one of `uniq`, `group`, `having` or `offset`, the generated query ignores them and that causes unintended records to be deleted. This solves the issue by restricting the deletion when those scopes are present. rails/rails#11985
* | | Remove unecessary requireArthur Neves2014-05-161-2/+0
| | |
* | | Remove the assignment for real this time.Zachary Scott2014-05-161-2/+2
| | | | | | | | | | | | | | | | | | cc: https://github.com/rails/rails/commit/a11e2fcff8cdc9691b977d8330abe63024f8c732#commitcomment-6353614 and 0369dbf
* | | prepend mutates the string so we can remove the assignmentRafael Mendonça França2014-05-161-1/+1
| | |
* | | Reuse the force_clear_transaction_record_stateRafael Mendonça França2014-05-161-1/+1
| | |
* | | Missed if :bomb:Rafael Mendonça França2014-05-161-1/+1
| | |
* | | Add a specific method to force the transaction record state clearRafael Mendonça França2014-05-161-5/+8
| | | | | | | | | | | | | | | | | | We are using that code path in only one place so we should not add a conditional to all the other cases. This will avoid performance regressions on the old paths.
* | | Clear transaction state if callback raise rollbackArthur Neves2014-05-151-1/+1
| | |
* | | Small refactoring on clear_transaction_record_stateArthur Neves2014-05-151-3/+5
| | | | | | | | | | | | | | | | | | Make sure when we clean the `@_start_transaction_state` var we do it in the same code-path. Also this makes `clear_transaction_record_state`, more consistent with `restore_transaction_record_state`
* | | Changed extract_limit in class Column to return correct mysql float and ↵Aaron Nelson2014-05-161-0/+2
| | | | | | | | | | | | double limits
* | | :scissors:Rafael Mendonça França2014-05-143-4/+0
| | |
* | | Methods of these modules are internalRafael Mendonça França2014-05-142-14/+14
| | | | | | | | | | | | | | | They should not be used on people application so they should not be present on the API documentation.
* | | Merge pull request #15088 from kares/shareable-modulesRafael Mendonça França2014-05-149-48/+52
|\ \ \ | | | | | | | | | | | | [postgres] remove (outer) sub-class declarations with nested modules/classes
| * | | PostgreSQLAdapter::Utils seems to be only used from a single spot - quite ↵kares2014-05-142-20/+19
| | | | | | | | | | | | | | | | redundant
| * | | move PostgreSQL's DatabaseStatements out of the PostgreSQLAdapter name-spacekares2014-05-142-7/+7
| | | |
| * | | PostgreSQL's SchemaStatements seems a could candidate for re-use (with AR-JDBC)kares2014-05-142-8/+7
| | | |
| * | | introduce AR::ConnectionAdapters::PostgreSQL for sharing modules (with AR-JDBC)kares2014-05-147-15/+21
| | | | | | | | | | | | ... 'shared' OID, ArrayParser and Cast helpers, also re-arranged Column's dependencies
* | | | Don't use Active Support where it is not needed.Rafael Mendonça França2014-05-141-1/+3
| | | | | | | | | | | | | | | | | | | | parent_name is a string of nil, never a blank string so we don't need to use presence.
* | | | Merge pull request #14871 from kassio/kb-fixes-namespaced-habtmRafael Mendonça França2014-05-141-1/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix how to compute class name on habtm namespaced. Conflicts: activerecord/CHANGELOG.md
| * | | | Fix how to compute class name on habtm namespaced.Kassio Borges2014-05-131-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Thank's for @laurocaetano for the help with tests. :smiley: Fixes #14709
* | | | | Merge pull request #15078 from nbudin/fix_merger_filter_binds_comparison_masterRafael Mendonça França2014-05-141-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make filter_binds filter out symbols that are equal to strings Conflicts: activerecord/CHANGELOG.md
| * | | | | Make filter_binds filter out symbols that are equal to stringsNat Budin2014-05-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ActiveRecord::Relation::Merger's filter_binds method does not filter out bind variables when one of the attribute nodes has a string name, but the other has a symbol name, even when those names are actually equal. This can result in there being more bind variables than placeholders in the generated SQL. This is particularly an issue for PostgreSQL, where this is treated as an error. This patch changes the filter_binds method to make it convert both attribute names to strings before comparing.
* | | | | | [ci skip]add updated information, ref[#522c0fd]Kuldeep Aggarwal2014-05-141-0/+2
| | | | | |
* | | | | | Fix inheritance of stored_attributes (fixes #14672)Jessica Yao2014-05-141-5/+14
| |_|/ / / |/| | | | | | | | | | | | | | [Brad Bennett, Jessica Yao, & Lakshmi Parthasarathy]
* | | | | remove count vareileencodes2014-05-131-4/+2
| | | | | | | | | | | | | | | | | | | | this change was unneccsary as nothing was gained from it
* | | | | rename delete_all_records to delete_or_nullify_all_recordseileencodes2014-05-133-8/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rename delete_all_records because this name better describes what the method is doing. We can then remove :all from the hm:t version and pull out the unoptimized call to load_target in delete_records and pass it directly.
* | | | | remove need for :all symboleileencodes2014-05-131-13/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactor delete_count method to only handle delete_all or nullify/nil cases and not destroy and switch to if/else rather than case statement. This refactoring allows removal of :all symbol usage.
* | | | | begin refactoring delete_records methodeileencodes2014-05-133-13/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactor by creating two methods delete_all_records and delete_records to be called by delete_all and delete (or destroy) respectively. This reduces the number of conditionals required to handle _how_ records get deleted. The new delete_count method handles how scope is applied to which delete action. A delete_all_records method also has to be called in has_many_through association because of how the methods are chained. This will be refactored later on.
* | | | | Merge pull request #15092 from kares/pg-array-parserRafael Mendonça França2014-05-132-27/+27
|\ \ \ \ \ | | | | | | | | | | | | [postgres] include PgArrayParser directly
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-03 14:54:15 +0000