diff options
| author | Dmytrii Nagirniak <dmytrii.nagirniak@rea-group.com> | 2015-12-01 08:02:17 +1100 |
|---|---|---|
| committer | Dmytrii Nagirniak <dmytrii.nagirniak@rea-group.com> | 2015-12-01 08:06:54 +1100 |
| commit | b83c097a3c6b01870e58c4da01702c2e4996ca0e (patch) | |
| tree | 8c8e8f24aef86c338f23b5f681b5f2d0160a0b69 /activerecord/test/fixtures/binaries.yml | |
| parent | 3f16a098452ee5d447142bd9a6f6045cb1fc83b4 (diff) | |
| download | rails-b83c097a3c6b01870e58c4da01702c2e4996ca0e.tar.gz rails-b83c097a3c6b01870e58c4da01702c2e4996ca0e.tar.bz2 rails-b83c097a3c6b01870e58c4da01702c2e4996ca0e.zip | |
Explain the connection pool error message better
The previous message was misleading (especially for Ops guys) when
diagnosing problems related to the database connection.
The message was suggesting that the connection cannot be obtained which
normally assumes the need to look at the database.
But this isn't the case as the connection could not be retrieved from
the application's internal connection pool.
The new message should make it more explicit and remove the confusion.
Diffstat (limited to 'activerecord/test/fixtures/binaries.yml')
0 files changed, 0 insertions, 0 deletions