Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | only log an error if there is a logger. fixes #5226 | Aaron Patterson | 2012-03-02 | 1 | -0/+9 |
| | |||||
* | Don't type-cast unknown types to YAML. | Stephen Celis | 2012-01-20 | 1 | -2/+2 |
| | |||||
* | remove checks for encodings availability | Sergey Nartimov | 2011-12-25 | 1 | -5/+1 |
| | |||||
* | deprecate String#encoding_aware? and remove its usage | Sergey Nartimov | 2011-12-24 | 1 | -2/+0 |
| | |||||
* | add the query to AR::Relation#explain output | Xavier Noria | 2011-11-25 | 1 | -0/+3 |
| | | | | | | | Rationale: this is more readable if serveral queries are involved in one call. Also, it will be possible to let AR log EXPLAINs automatically in production mode, where queries are not even around. | ||||
* | fixing tests on ruby 1.8 | Aaron Patterson | 2011-11-20 | 1 | -1/+3 |
| | |||||
* | pushing caching and visitors down to the connection | Aaron Patterson | 2011-11-19 | 1 | -0/+1 |
| | |||||
* | revises EXPLAIN tests for SQLite3 | Xavier Noria | 2011-11-06 | 1 | -3/+3 |
| | | | | | | | | | | The output in Travis is a bit different. The SQLite documentation (http://www.sqlite.org/eqp.html) warns output may change dramatically between releases. I do not want to mock the result set because I want a real EXPLAIN to happen. I prefer a test that may fail in future releases than a test that may give false positives in future releases. | ||||
* | implements AR::Relation#explain | Xavier Noria | 2011-11-05 | 1 | -0/+23 |
| | | | | | | | | | | | | | | | | | | | This is a first implementation, EXPLAIN is highly dependent on the database and I have made some compromises. On one hand, the method allows you to run the most common EXPLAIN and that's it. If you want EXPLAIN ANALYZE in PostgreSQL you need to do it by hand. On the other hand, I've tried to construct a string as close as possible to the ones built by the respective shells. The rationale is that IMO the user should feel at home with the output and recognize it at first sight. Per database. I don't know whether this implementation is going to work well. Let's see whether people like it. | ||||
* | Transactional fixtures enlist all active database connections. | Jeremy Kemper | 2011-10-05 | 1 | -0/+4 |
| | | | | You can use multiple databases in your tests without disabling transactional fixtures. | ||||
* | LRU cache in mysql and sqlite are now per-process caches. | Aaron Patterson | 2011-09-07 | 1 | -0/+24 |
| | |||||
* | Force binary data inserted for a string data type to utf-8 and log an | Aaron Patterson | 2011-08-25 | 1 | -0/+16 |
| | | | | | | | | error. Strings tagged as binary will be stored in sqlite3 as blobs. It is an error to insert binary data to a string column, so an error is emitted in the log file. People are highly encouraged to track down the source of the binary strings and make sure that the encoding is set correctly before inserting to the database. | ||||
* | bigdecimal should be typecast to a float on sqlite3. fixes #2162 | Aaron Patterson | 2011-07-20 | 1 | -1/+1 |
| | |||||
* | please use ruby -I lib:test path/to/test.rb, or export RUBY_OPT | Aaron Patterson | 2011-06-06 | 3 | -3/+3 |
| | |||||
* | Refactor Active Record test connection setup. Please see the ↵ | Jon Leighton | 2011-06-04 | 3 | -3/+3 |
| | | | | 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. | ||||
* | inserting big decimals as strings works consistently among dbs, so use ↵ | Aaron Patterson | 2011-04-14 | 1 | -1/+1 |
| | | | | string form | ||||
* | adding a type cast method for prepared statements | Aaron Patterson | 2011-04-14 | 1 | -0/+93 |
| | |||||
* | use index based substitution for bind parameters | Aaron Patterson | 2011-04-13 | 1 | -1/+1 |
| | |||||
* | adding exec_insert for postgresql | Aaron Patterson | 2011-04-11 | 1 | -0/+2 |
| | |||||
* | adding exec_insert to sqlite3 | Aaron Patterson | 2011-04-11 | 1 | -0/+12 |
| | |||||
* | moving sqlite_adapter_tests to sqlite3_adapter_test so that the tests are ↵ | Aaron Patterson | 2011-04-08 | 1 | -0/+215 |
| | | | | actually run. :bomb: | ||||
* | define_attr_method must serialize nil correctly | Aaron Patterson | 2010-12-20 | 1 | -0/+5 |
| | |||||
* | converted exec to exec_query for sqlite | Aaron Patterson | 2010-11-05 | 1 | -12/+12 |
| | |||||
* | refactoring tests | Aaron Patterson | 2010-10-26 | 1 | -36/+20 |
| | |||||
* | type casting bound value based on column associated with value | Aaron Patterson | 2010-10-26 | 1 | -0/+18 |
| | |||||
* | exec returns an AR::Result | Aaron Patterson | 2010-10-26 | 1 | -0/+35 |
| | |||||
* | adding bind value substitution | Aaron Patterson | 2010-10-26 | 1 | -0/+9 |
| | |||||
* | Move sqlite to sqlite3 for this tests to be run only on sqlite3 adapter | Santiago Pastorino | 2010-06-28 | 2 | -0/+136 |
Signed-off-by: José Valim <jose.valim@gmail.com> |