rspec 返回“PG::Error:错误:关系“table_name"；不存在" [英] rspec returns "PG::Error: ERROR: relation "table_name" does not exist"

问题描述

在 rvm、rspec 2.8.0、rails 3.0.6 和 pg 0.13.2 上，环境是 REE(2011.12).在 CentOS 5.6 上使用 PostgreSQL 8.3.17.db:migrate 工作正常.但是 rspec 有以下错误.

Environment is REE(2011.12) on rvm, rspec 2.8.0, rails 3.0.6, and pg 0.13.2. Using PostgreSQL 8.3.17 on CentOS 5.6. The db:migrate have work correctly. But rspec have got following error.

1) ApiController articles OK
 Failure/Error: Unable to find matching line from backtrace
 ActiveRecord::StatementInvalid:
   PG::Error: ERROR:  relation "table_name" does not exist
   : DELETE FROM "table_name"

我正在将我的项目从带有 rspec 1.x 系列的 rails 2.3.5 更新到带有 rspec2 的 rails 3.0.复制了所有的 rspec 测试，我已经合并了旧的 spec_helper.rb 和新的(它是由 rails g rspec:install 生成的).

I'm updating my project from rails 2.3.5 with rspec 1.x series to rails 3.0 with rspec2. Copied all rspec tests, and I have merged old spec_helper.rb and new one(It was generated rails g rspec:install).

ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'rspec/autorun'

Dir[Rails.root.join("spec/support/**/*.rb")].each {|f| require f}

RSpec.configure do |config|

  config.fixture_path = "#{::Rails.root}/spec/fixtures"
  config.use_transactional_fixtures = true

end

我阅读了有关此错误的类似问题.所以我尝试了 rake db:test:prepare 或 rake db:test:load，但没有解决.你有什么主意吗?看起来测试没有在测试数据库上运行......我该怎么办?:(

I read similar question about this error.So I tried rake db:test:prepare or rake db:test:load, But It's not resolve. Do you have any idea? It looks like the test hasn't run on test database... How do I do? :(

推荐答案

我在两个实例中遇到过这种情况(2012 年 6 月 13 日更新):

I've run into this in two instances (updated 6/13/2012):

我还没有迁移我的测试数据库...

I haven't yet migrated my test database...

rake db:migrate

...你需要在 db:test:prepare 和 db:test:load 之前做.

...which you need to do before both db:test:prepare and db:test:load.

当您调用 rspec 时，它应该为您准备和加载您的数据库.您不应该手动执行此操作.

When you invoke rspec it should prepare and load your database for you anyway. You shouldn't have to do that by hand.

我的迁移中有一个错字.我不小心把参数列表中的表名和列名颠倒了.

A typo in my migration. I accidentally reversed my table and column names in the parameter list.

Rails 3.1 项目的迁移:

A migration on a Rails 3.1 project:

def change
  add_column :had_import_errors, :studies, :boolean, :default => false
  add_column :import_data_cache, :studies, :text
end

...这是错误，因为has_import_errors 和import_data_cache 是我的列名，因此它们应该排在第二位，而不是第一位.

...which is wrong, because has_import_errors and import_data_cache are my column names, and they therefore should come second, not first.

正确的迁移，首先是表名是:

The correct migration, with the table name first was:

def change
  add_column :studies, :had_import_errors, :boolean, :default => false
  add_column :studies, :import_data_cache, :text
end

这篇关于rspec 返回“PG::Error:错误:关系“table_name"；不存在"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！