This project is archived and is in readonly mode.
Incorrect table_name evaluation in tests when using legacy database
Reported by Yuriy Hrytsyuk | June 11th, 2008 @ 02:02 PM
in app/models/product.rb:
class Product < ActiveRecord::Base
set_table_name "product_legacy_table"
end
~/sandbox$ rake test ...skiped... 1) Error: test_truth(ProductTest): ActiveRecord::StatementInvalid: SQLite3::SQLException: no such table: products: DELETE FROM "products" WHERE 1=1 ...skiped...
Patch included
Comments and changes to this ticket
-
Rohit Arondekar October 6th, 2010 @ 06:44 AM
- State changed from new to stale
- Tag set to 2.1, activerecord, bug, patch, tests
- Importance changed from to
Marking ticket as stale. If this is still an issue please leave a comment with suggested changes, creating a patch with tests, rebasing an existing patch or just confirming the issue on a latest release or master/branches.
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
- 4263 Unit test fail when using non-standard table names This error has been reported in tickets #389 and #307. Th...
- 4263 Unit test fail when using non-standard table names The author of ticket #389 writes “patch included”, howeve...
- 4263 Unit test fail when using non-standard table names https://rails.lighthouseapp.com/projects/8994/tickets/30...