aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases
Commit message (Collapse)AuthorAgeFilesLines
* More tests deep including through habtmArun Agrawal2011-12-211-0/+7
| | | fixes #3183
* 'with_kcode' removed. Arun Agrawal2011-12-212-25/+19
| | | | Testing Sandbox removed.
* Removed test which works only < 1.9Arun Agrawal2011-12-213-34/+0
|
* No Ruby 1.8 stuff. No more checks in code.Arun Agrawal2011-12-212-25/+0
|
* skip hstore tests on PG databases that do not have hstoreAaron Patterson2011-12-201-2/+8
|
* making sure updates workAaron Patterson2011-12-201-7/+13
|
* hstores can cycleAaron Patterson2011-12-201-2/+26
|
* can create hstore records via AR APIAaron Patterson2011-12-201-0/+7
|
* multiple key / values workAaron Patterson2011-12-201-0/+6
|
* PostgreSQL hstore types are automatically deserialized from the database.Aaron Patterson2011-12-201-0/+16
|
* pg columns should understand the hstore typeAaron Patterson2011-12-201-0/+24
|
* remove more uses of deprecated loggersKarunakar (Ruby)2011-12-211-2/+2
|
* Merge pull request #4035 from lest/date-type-castAaron Patterson2011-12-201-0/+8
|\ | | | | handle not only strings in date type cast
| * handle not only strings in date type castSergey Nartimov2011-12-191-0/+8
| |
* | remove more uses of deprecated logger methodsAaron Patterson2011-12-193-6/+8
|/
* Merge pull request #4014 from lest/bypass-preloading-for-ids-readerJon Leighton2011-12-181-0/+6
|\ | | | | bypass preloading for ids_reader
| * bypass preloading for ids_readerSergey Nartimov2011-12-181-0/+6
| | | | | | | | | | when fetching ids for a collection, bypass preloading to avoid the unnecessary performance overhead
* | call scope within unscoped to prevent duplication of where valuesSergey Nartimov2011-12-171-0/+5
|/
* Delete obsolete commentJon Leighton2011-12-161-1/+0
|
* Should clear the primary keys cache alsoJon Leighton2011-12-161-1/+5
|
* Don't store defaults in the schema cacheJon Leighton2011-12-162-1/+2
|
* Cache columns at the model level.Jon Leighton2011-12-164-21/+34
| | | | Allows two models to use the same table but have different primary keys.
* Let AttributeMethods do its own including etcJon Leighton2011-12-151-4/+2
|
* Split out most of the AR::Base code into separate modules :cake:Jon Leighton2011-12-151-13/+0
|
* Fix #3987.Jon Leighton2011-12-151-0/+10
|
* Allow nested attributes in associations to update values in it's owner ↵Andrew Kaspick2011-12-141-0/+5
| | | | object. Fixes a regression from 3.0.x
* Remove that there copy/pasted code :bomb:Jon Leighton2011-12-141-5/+0
|
* Don't try to autosave nested assocs. Fixes #2961.Jon Leighton2011-12-141-0/+14
|
* Stop the build asploding on 1.8.7Jon Leighton2011-12-141-0/+4
|
* Add return for 1.8.7Jon Leighton2011-12-141-1/+1
|
* Unfluff the CI.Jon Leighton2011-12-141-1/+1
| | | | | | | | | | | | | | | With transactional fixtures enabled, the session records would end up in @_current_transaction_records, and at the end of the transaction, methods would be called on them that would trigger method_missing and trigger attribute methods to be generated. However, at this point the sessions table would not exist, and the columns were not cached, so an exception would be raised because we can't find the columns to generate attribute methods for. Not sure exactly why this didn't crop up before but there have been changes to the schema cache code and perhaps that means that column data that was cached previously at that point is now uncached.
* Revert naive O(1) table_exists? implementation.Jon Leighton2011-12-131-0/+1
| | | | | | | | | | It was a bad idea to rescue exceptions here. This can interfere with transaction rollbacks which seems to be the cause of current CI failure. Instead, each adapter should implement its own DB-specific O(1) implementation, and we fall back on the generic, slower, implementation otherwise.
* Errno::ENOENT error makes more sense when a file cannot be foundAaron Patterson2011-12-101-1/+1
|
* Allow to filter migrations by passing a blockPiotr Sarnacki2011-12-091-0/+18
| | | | | | | | | | Example: ActiveRecord::Migrator.migrate(path) do |migration| migration.name =~ /User/ end The above example will migrate only migrations with User in the name
* Use `table_exists?` from the schema cache.Aaron Patterson2011-12-092-3/+4
|
* Compare migrations for copying only by name and scopePiotr Sarnacki2011-12-091-26/+1
|
* Add suffix for migrations copied from enginesPiotr Sarnacki2011-12-091-23/+23
|
* String#to_a is not available in 1.9Piotr Sarnacki2011-12-091-1/+1
|
* Run also migrations in subdirectories.Piotr Sarnacki2011-12-091-0/+9
| | | | | With this commit, ActiveRecord will also look for migrations in db/migrate subdirectories.
* Ignore origin comment when checking for duplicates on Migration.copyPiotr Sarnacki2011-12-091-3/+29
| | | | | | | 49ebe51 fixed copying migrations, but existing migrations would still trigger warnings. The proper way to compare migrations is to ignore origin lines - if migration is identical it means that we can silently skip it, regardless where it comes from.
* Fix copying migrations from enginesPiotr Sarnacki2011-12-091-0/+21
| | | | | | | | | | There was a bug in ActiveRecord::Migration.copy method, which prevented adding special comment about the origin of migration. Because of that, the check if migration is identical or if it's not and should be skipped was always saying that migration is skipped, which was causing additional useless warnings about skipped migrations.
* Fix #3890. (Calling proxy_association in scope chain.)Jon Leighton2011-12-081-0/+6
|
* Regexp.union seems to have different results in 1.8Aaron Patterson2011-12-081-3/+3
|
* Fix broken test_exists_query_logging from the table_exists? changeJon Leighton2011-12-081-0/+1
|
* moving ignored regexp to the instanceAaron Patterson2011-12-071-6/+8
|
* speeding up ignored sql testingAaron Patterson2011-12-071-1/+4
|
* avoid deprecated methodsAaron Patterson2011-12-061-1/+1
|
* add prefix and suffix to renamed tables, closes #1510Vasiliy Ermolovich2011-12-061-0/+31
|
* Merge pull request #3854 from exviva/validates_associated_marked_for_destructionJosé Valim2011-12-041-0/+10
|\ | | | | Do not validate associated records marked for destruction
| * Do not validate associated records marked for destructionOlek Janiszewski2011-12-051-0/+10
| | | | | | | | | | | | The main reason for this change is to fix a bug where `validates_associated` would prevent `accepts_nested_attributes_for` with `allow_destroy: true` from destroying invalid associated records.
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 08:40:08 +0000