aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/fixtures.rb
Commit message (Collapse)AuthorAgeFilesLines
* Fixed typo in comment about MAX_ID.Vajrasky Kok2014-02-231-1/+1
|
* Update deprecation warning to give more information about callerT.J. Schuck2014-01-161-2/+2
|
* Revert "ask the fixture set for the sql statements"Aaron Patterson2014-01-091-12/+10
| | | | | | | | | This reverts commit 026d0555685087845b74dd87a0417b5a164b1c13. Conflicts: activerecord/lib/active_record/fixtures.rb Fixes #13383
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2013-12-201-1/+1
|\
| * Typos. return -> returns. [ci skip]Lauro Caetano2013-12-031-1/+1
| |
* | Introduce a context for rendering fixtures ERB.Victor Costan2013-12-031-0/+32
|/ | | | | | | | | | Fixture files are passed through an ERB renderer before being read as YAML. The rendering is currently done in the context of the main object, so method definitons leak into other fixtures, and there is no clean place to define fixture helpers. After this commit, the ERB renderer will use a new subclass of ActiveRecord::FixtureSet.context_class each time a fixture is rendered.
* ask the fixture set for the sql statementsAaron Patterson2013-11-041-10/+12
|
* remove HABTM special cases from the fixturesAaron Patterson2013-10-021-12/+0
|
* let the class cache object clean up user inputAaron Patterson2013-09-091-8/+20
|
* Fix fixtures regression that required table names to map to classes only, ↵Jeremy Kemper2013-09-081-1/+1
| | | | not class names
* use polymorphic proxies to remove duplicate codeAaron Patterson2013-09-061-24/+43
|
* reduce duplication somewhatAaron Patterson2013-09-061-14/+14
|
* make the duplicate code more similarAaron Patterson2013-09-061-4/+10
|
* auto link hm:t fixture join tables like habtmAaron Patterson2013-09-061-0/+16
|
* don't depend on object state when reading fixture filesAaron Patterson2013-09-061-8/+7
|
* ensure @model_class is initializedAaron Patterson2013-09-061-0/+1
|
* no need to dupAaron Patterson2013-09-051-1/+1
|
* push logic outside the FixtureSet constructorAaron Patterson2013-09-051-3/+3
|
* only construct the FixtureSet with AR modelsAaron Patterson2013-09-051-2/+11
|
* push constant lookup in the a cache objectAaron Patterson2013-09-051-2/+21
|
* Add config to method calls in fixtures.wangjohn2013-08-261-23/+26
| | | | | | | Allows you to change your configuration for calls to `table_name_prefix`, `table_name_suffix`, and `pluralize_table_names`. The default configuration is still ActiveRecord::Base, but you are now able to change the configuration easily.
* Removing instances of string class_names in fixtures.wangjohn2013-08-241-3/+6
| | | | | | | Also, constantizing the default_fixture_model_name when it gets loaded in from the file. Later, when the class_name is passed to a new FixtureSet, a deprecation warning will occur if the class_name is a string.
* Deprecating passing strings as class name in fixtures.wangjohn2013-08-231-7/+1
|
* load fixtures from linked foldersKassio Borges2013-08-051-2/+2
|
* extract habtm handling to a methodAaron Patterson2013-08-011-8/+12
|
* Remove deprecated `ActiveRecord::Fixtures.find_table_name` in favour of ↵Vipul A M2013-07-031-6/+0
| | | | `ActiveRecord::Fixtures.default_fixture_model_name`.
* fixture setup does not rely on `AR::Base.configurations`.Yves Senn2013-06-151-4/+0
| | | | | | | | As you can also configure your database connection using `ENV["DATABASE_URL"]`, the fixture setup can't reply on the `.configurations` Hash. As the fixtures are only loaded when ActiveRecord is actually used (`rails/test_help.rb`) it should be safe to drop the check for an existing configuration.
* reverse comparison because of strange AS behaviorAaron Patterson2013-05-211-1/+1
| | | | http://tenderlovemaking.com/2013/05/21/one-danger-of-freedom-patches.html
* stop depending on callbacksAaron Patterson2013-04-041-6/+12
|
* Allows setting fixture_path to a PathnameAlexander Murmann and Can Berk Güder2013-03-211-1/+1
|
* fix example of setting DEFAULTS in fixturesJonathan Garvin2013-01-161-2/+2
|
* These are already required through AS/railsAkira Matsuda2013-01-071-2/+0
| | | | | | * dependencies/autoload * concern * deprecation
* Fix argument name in fixtures methodCarlos Antonio da Silva2012-12-181-1/+1
| | | | Relatedo to 8e44c93b4c0e4b1bdd0fca13b79f5be1088d6959.
* Revert "use File.basename to get the filename minus .yml"Aaron Patterson2012-12-181-4/+3
| | | | | | | This reverts commit 00c5342d96a3677c0a6a2bb8316c76182f5bdfdd. Conflicts: activerecord/lib/active_record/fixtures.rb
* Remove useless check of AR being defined from teardown fixturesCarlos Antonio da Silva2012-11-271-5/+4
| | | | | | | We are already in the AR namespace, there's no way for it to be undefined. See the cousin commit 13e72db77063f57c3028a906690d42fb068845bb Refactor a bit teardown fixtures to avoid two conditionals.
* Add a deprecation before removing find_table_nameAlexey Muranov2012-11-171-0/+6
| | | The `ActiveRecord::Fixtures::find_table_name` method was removed from "master" almost a year ago, but it was never deprecated. Here it comes back, more dead than alive.
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-11-171-2/+2
|\ | | | | | | | | Conflicts: actionpack/lib/action_dispatch/routing/redirection.rb
| * 1.9 Syntax related changesAvnerCohen2012-11-101-2/+2
| |
* | Properly deprecate ConnectionHandler#connection_poolsJon Leighton2012-11-091-1/+1
|/ | | | | | | | Rather than just changing it and hoping for the best. Requested by @jeremy: https://github.com/rails/rails/commit/ba1544d71628abff2777c9c514142d7e9a159111#commitcomment-2106059
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-11-031-0/+1
|\ | | | | | | | | | | | | Conflicts: actionpack/lib/action_controller/metal/mime_responds.rb activerecord/lib/active_record/attribute_methods.rb guides/source/working_with_javascript_in_rails.md
| * nodoc deprecated AR::Fixtures constant [ci skip]Francesco Rodriguez2012-10-211-0/+1
| |
* | Remove ActiveRecord::ModelJon Leighton2012-10-261-1/+1
|/ | | | | | | | | | In the end I think the pain of implementing this seamlessly was not worth the gain provided. The intention was that it would allow plain ruby objects that might not live in your main application to be subclassed and have persistence mixed in. But I've decided that the benefit of doing that is not worth the amount of complexity that the implementation introduced.
* Remove the leading :: constant qualifier in the ActiveRecord::Fixtures ↵Jeremy Kemper2012-10-101-1/+1
| | | | deprecation message
* Move/rename files to follow naming conventionsAlexey Muranov2012-10-071-1/+1
|
* Deprecate "Fixtures" constantAlexey Muranov2012-10-071-0/+8
|
* Rename "Fixtures" class to "FixtureSet"Alexey Muranov2012-10-071-17/+17
| | | | Rename `ActiveRecord::Fixtures` class to `ActiveRecord::FixtureSet`. Instances of this class normally hold a collection of fixtures (records) loaded either from a single YAML file, or from a file and a folder with the same name. This change make the class name singular and makes the class easier to distinguish from the modules like `ActiveRecord::TestFixtures`, which operates on multiple fixture sets, or `DelegatingFixtures`, `::Fixtures`, etc., and from the class `ActiveRecord::Fixture`, which corresponds to a single fixture.
* Move transaction joinability into the transaction objectJon Leighton2012-09-151-3/+2
|
* Start to tease out transaction handling into a state machineJon Leighton2012-09-151-6/+2
|
* One hash is enoughJon Leighton2012-08-311-1/+1
| | | | We don't need separate @class_to_pool and @connection_pool hashes.
* load active_support/core_ext/object/blank in active_support/railsXavier Noria2012-08-021-1/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-05 02:22:13 +0000