This project is archived and is in readonly mode.
Fix test_rename_nonexistent_column for PostgreSQL
Reported by Tarmo Tänav | July 14th, 2008 @ 07:48 AM | in 2.x
2e1b56c93745bf0513e449e95830edd390abfaf2 added a test for a mysql change which fails in postgresql. This happens because mysql and postgresql raise different exceptions for invalid sql. The fix is simply to assert the expected exception class.
Comments and changes to this ticket
-
Repository July 14th, 2008 @ 09:41 PM
- State changed from “new” to “resolved”
(from [8f72bc92e20b1242272714f253e23b256761ec1a]) Fixed test_rename_nonexistent_column for PostgreSQL
Also fixed ability to run migration_test.rb alone
[#616 state:resolved]
-
Repository July 15th, 2008 @ 11:56 PM
(from [8a548e4fa8587f24f214195194c1d6974454b656]) Fixed test_rename_nonexistent_column for PostgreSQL
Also fixed ability to run migration_test.rb alone
[#616 state:resolved]
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>
Repository
Tarmo Tänav