aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases/session_store
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Use `table_exists?` from the schema cache.Aaron Patterson2011-12-091-0/+1
|
* Reset column info when messing with columns.Jon Leighton2011-09-131-0/+2
| | | | | | | We are subclassing Session here, but messing with the columns will affect the attribute methods defined on the Session superclass, and therefore other tests, unless we properly isolate it by resetting column info before and after the test run.
* please use ruby -I lib:test path/to/test.rb, or export RUBY_OPTAaron Patterson2011-06-062-2/+2
|
* Refactor Active Record test connection setup. Please see the ↵Jon Leighton2011-06-042-2/+2
| | | | RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases.
* Puts ActiveRecord::SessionStore attributes in white list, fixes #483slainer682011-05-101-0/+6
|
* share column cache among subclasses, only look up columns per AR::Base ↵Aaron Patterson2011-02-011-0/+1
| | | | subclass once
* In a number of places in the tests, we only need to turn off transactional ↵Jon Leighton2011-01-111-1/+1
| | | | fixtures when the DB does not support savepoints. This speeds the test run up by about 8-9% on my computer, when running rake test_sqlite3_mem :)
* use persisted? instead of new_record? wherever possibleDavid Chelimsky2010-11-091-2/+2
| | | | | | | | | | | - persisted? is the API defined in ActiveModel - makes it easier for extension libraries to conform to ActiveModel APIs without concern for whether the extended object is specifically ActiveRecord [#5927 state:committed] Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
* do not execute the session tests within transactionsAaron Patterson2010-07-251-0/+2
|
* testing sqlbypass destroy. caching connection during destroyAaron Patterson2010-07-231-0/+9
|
* refactoring class methods to a moduleAaron Patterson2010-07-221-2/+5
|
* session_id is a VARCHARSantiago Pastorino2010-07-221-5/+5
|
* adding a test for session saveAaron Patterson2010-07-221-0/+10
|
* testing loaded? method and reducing funcallsAaron Patterson2010-07-211-0/+10
|
* testing new_record? and converting to an attributeAaron Patterson2010-07-211-0/+5
|
* starting sql bypass test, fixing create_table and drop_table!Aaron Patterson2010-07-211-0/+22
|
* initializing instance variablesAaron Patterson2010-07-211-0/+63