This project is archived and is in readonly mode.
catch_schema_changes in the sqlite3 adapter doesn't actually do anything
Reported by Aaron Patterson | June 27th, 2010 @ 01:05 AM | in 3.x
catch_schema_changes in the sqlite3 adapter is supposed to catch "database schema changed" exceptions, reconnect to the database, then retry the statement. The implementation of reconnect! for the sqlite adapter simply uses the abstract adapter's reconnect method. The abstract reconnect method doesn't do anything to the sqlite adapter. If people were actually getting this error, they would end up in an infinite loop.
The attached patch removes that method.
Comments and changes to this ticket
-
Aaron Patterson June 27th, 2010 @ 01:07 AM
- no changes were found...
-
Repository June 27th, 2010 @ 03:56 AM
- State changed from new to resolved
(from [abd568bf1c48e9082c0be7407eca1155c5fe0599]) removing useless code. [#4988 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/abd568bf1c48e9082c0be7407eca11...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 4988 catch_schema_changes in the sqlite3 adapter doesn't actually do anything (from [abd568bf1c48e9082c0be7407eca1155c5fe0599]) removin...