rails/activerecord/test
Matthew Draper c4bdca19a7 Use connection-specific bytea escaping
In our normal usage, it's rare for this to make a difference... but is
more technically correct.

As well as a spec that proves this is a good idea, let's also add a more
sane-looking one that just covers basic to_sql functionality. There
aren't many places where we actually use escape_bytea, but that's one
that won't be going away.
2014-04-08 00:36:30 +09:30
..
active_record/connection_adapters Ensure disconnecting or reconnecting resets the transaction state 2012-09-15 00:03:04 +01:00
assets Added test to illustrate bad binary blobs. 2012-01-31 13:45:00 -06:00
cases Use connection-specific bytea escaping 2014-04-08 00:36:30 +09:30
fixtures Extend fixture label replacement to allow string interpolation 2014-03-15 22:11:36 -04:00
migrations activerecord: Initialize Migration with version from MigrationProxy. 2014-01-06 10:46:35 -05:00
models Fix the test defining the models in the right place 2014-04-04 19:44:17 -03:00
schema Merge pull request #14579 from senny/pg/remove_string_limit 2014-04-04 19:51:35 -03:00
support Add ConnectionHelper to refactor tests. 2014-04-03 01:06:43 -07:00
.gitignore Refactor Active Record test connection setup. Please see the 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. 2011-06-04 23:47:03 +01:00
config.example.yml Simulated & actual (manual/skipped) PostgreSQL auto-reconnection tests. 2012-07-16 09:55:20 -07:00
config.rb