diff options
| author | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2013-12-19 01:44:01 -0800 |
|---|---|---|
| committer | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2013-12-19 01:44:01 -0800 |
| commit | 5b0fc1a007522e9d41faf364f74426be2b9e3f63 (patch) | |
| tree | 2e5620fdfb2a0043208b5b4f3c90c8d35dd10031 /activesupport/test | |
| parent | a3ebe7f3a741fee71c419a0774adb28bd9de0e8e (diff) | |
| parent | f8b4110f009a8d509f0350da4c1388c5a5bb4a2d (diff) | |
| download | rails-5b0fc1a007522e9d41faf364f74426be2b9e3f63.tar.gz rails-5b0fc1a007522e9d41faf364f74426be2b9e3f63.tar.bz2 rails-5b0fc1a007522e9d41faf364f74426be2b9e3f63.zip | |
Merge pull request #13393 from matthewd/fix_pg_range_tests
Fix PostgreSQL range tests on fresh DB
Correcting the name of the table we're creating is self-explanatory.
But we must also move away from the low IDs, because we're not touching the freshly-created primary key sequence; when the time comes, @new_range will be assigned an ID of 1.
Diffstat (limited to 'activesupport/test')
0 files changed, 0 insertions, 0 deletions