blocks|key|4675410|text|我有这个问题。只需重新启动Rails+Server，它就应该可以工作了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4675411|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this issue. Just restart the Rails Server and it should work

blocks|key|4675451|text|这个问题是在我的测试环境中发生的，并且是由于每个测试都封装在自己的事务中而导致的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4675452|我使用的是javascript+gem，并对其进行了配置，以便在使用database_cleaner的情况下不将测试包装在事务中。因此，为了解决这个问题，我在导致这个问题的每个规范中添加了js:+true。(尽管规范实际上并没有使用javascript，但这是确保测试不会被包装在事务中的最方便的方法。我确信有更少的黑客方式来做到这一点)。|offset|length|style|CODE|4675453|以下是来自spec/support/database_cleaner.rb的database_cleaner配置，以供参考|4675454|RSpec.configure+do+%7Cconfig%7C

++config.before(:suite)+do
++++DatabaseCleaner.clean_with+:deletion
++end

++config.before(:each)+do
++++DatabaseCleaner.strategy+=+:transaction
++end

++config.before(:each,+:js+=>+true)+do
++++DatabaseCleaner.strategy+=+:deletion
++end

++config.before(:each)+do
++++DatabaseCleaner.start
++end

++config.after(:each)+do
++++DatabaseCleaner.clean
++end

end|code-block|syntax|javascript|4675455|如果您没有使用database_cleaner，那么测试将被包装在事务中的原因可能是因为在spec/spec_helper.rb中将use_transactional_fixtures选项设置为true。尝试将其设置为false。|4675456|entityMap^0|0|2M|8|0|5|W|0|0|19|J|1U|Q|2P|4|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$]]

This issue was occurring in my test environment, and was caused by the fact that each test was wrapped in its own transaction.

I was using the database_cleaner gem, and have it configured so as NOT to wrap tests in a transaction if they use javascript. So to solve the issue, I added <code>js: true</code> to each spec that was causing this problem. (Even thought the specs did not actually use javascript, this was the most convenient way to ensure that the tests would not be wrapped in a transaction. I am sure there are less hack-ish ways of doing so, though).

For reference, here is the database_cleaner config from <code>spec/support/database_cleaner.rb</code>:

<pre><code>RSpec.configure do |config|

 config.before(:suite) do
 DatabaseCleaner.clean_with :deletion
 end

 config.before(:each) do
 DatabaseCleaner.strategy = :transaction
 end

 config.before(:each, :js =&gt; true) do
 DatabaseCleaner.strategy = :deletion
 end

 config.before(:each) do
 DatabaseCleaner.start
 end

 config.after(:each) do
 DatabaseCleaner.clean
 end

end
</code></pre>

If you are not using database_cleaner, then probably the reason the tests would be wrapped in transactions would be that the <code>use_transactional_fixtures</code> option is set to <code>true</code> in <code>spec/spec_helper.rb</code>. Try setting it to false.

blocks|key|4675599|text|你可以看到postgresql日志中到底发生了什么，我花了很多时间深入研究这个问题，最后发现我们滥用upsert+gem导致了PG错误，只有在postgresql日志中才有发生情况的真实信息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4675600|https://github.com/seamusabshere/upsert/issues/39|offset|length|4675601|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

you can see what really going on in postgresql log, I spend a lot of time to dig into this issue, and finally find out that we misuse upsert gem cause a PG error, only in postgresql log have the real info of what's going on 

<a href="https://github.com/seamusabshere/upsert/issues/39" rel="noreferrer">https://github.com/seamusabshere/upsert/issues/39</a>

blocks|key|4675657|text|在我的规范中引用一个不再存在的列时，我遇到了这个错误。确保您的数据库是最新的，并且您的代码不会期望不存在的列。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4675658|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've run into this error when referencing a column in my specs that no longer exists. Make sure your database is up to date and your code doesn't expect a column that doesn't exist.

blocks|key|4675707|text|在将Rails从4.2.2升级到4.2.5之后，我遇到了类似的问题，我不得不升级pg+gem，然后问题开始出现|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4675708|9)+WorkPolicy#is_publicly_viewable?+is+publicly+visible+hides+work+if+deleted
+++++Failure/Error:+before+{+DatabaseCleaner.clean_with+:deletion+}
+++++ActiveRecord::StatementInvalid:
+++++++PG::InFailedSqlTransaction:+ERROR:++current+transaction+is+aborted,+commands+ignored+until+end+of+transaction+block
+++++++:+++++++++++++SELECT+tablename
+++++++++++++++++++FROM+pg_tables
+++++++++++++++++++WHERE+schemaname+=+ANY+(current_schemas(false))|code-block|syntax|javascript|4675709|Teddy+Widom+Answer在这个意义上是正确的，只是总结一下问题：|4675710|有时，当您使用DatabaseCleaner.clean_with+:deletion时，您可能会干扰PostgreSQL事务。|4675711|因此，我的解决方案是在由DatabaseCleaner.clean_with+:truncation引起的部分测试中替换DatabaseCleaner.clean_with+:deletion|4675712|还有一件事可以用来搜索人们。如果您注意到此堆栈跟踪：|4675713|An+error+occurred+in+an+`after(:context)`+hook.
ActiveRecord::StatementInvalid:+PG::UndefinedColumn:+ERROR:++column+"table_rows"+does+not+exist
LINE+1:+...ion_schema.tables+WHERE+table_schema+=+'test'+AND+table_rows...
%5E|4675714|此问题可能会导致...it|4675715|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/22383251/473040^0|14|2|0|0|0|I|0|0|7|10|0|C|12|1O|10|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|M|3|N|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1K|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1M|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

Had similar problem after upgrading Rails from 4.2.2 to 4.2.5 I had to upgrade <code>pg</code> gem and problem start happening

<pre><code>9) WorkPolicy#is_publicly_viewable? is publicly visible hides work if deleted
 Failure/Error: before { DatabaseCleaner.clean_with :deletion }
 ActiveRecord::StatementInvalid:
 PG::InFailedSqlTransaction: ERROR: current transaction is aborted, commands ignored until end of transaction block
 : SELECT tablename
 FROM pg_tables
 WHERE schemaname = ANY (current_schemas(false))
</code></pre>

<a href="https://stackoverflow.com/a/22383251/473040">Teddy Widom Answer</a> is right in this sense, just to sum the problem:

Sometimes when you use <code>DatabaseCleaner.clean_with :deletion</code> you may be interfering PostgreSQL transaction. 

So solution for me was to replace <code>DatabaseCleaner.clean_with :deletion</code> in parts of the tests where this was caused with <code>DatabaseCleaner.clean_with :truncation</code>

Just one more thing for googling people. If you are noticing this stack trace:

<pre><code>An error occurred in an `after(:context)` hook.
ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR: column "table_rows" does not exist
LINE 1: ...ion_schema.tables WHERE table_schema = 'test' AND table_rows...
^
</code></pre>

...it may be caused by this problem

blocks|key|169887|text|在我的例子中，我收到这个错误只是因为我没有整理我的测试数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169888|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I received this error simply because I had not rake'd my test db.

blocks|key|4675797|text|在我的例子中，/usr/local/var/postgres/postgresql.conf的Postgres配置的日期类型是dmy的国际格式|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4675798|将日期类型更改为mdy的美国格式为我解决了这个问题。|4675799|entityMap^0|7|13|1R|3|0|8|3|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

In my case the Postgres configuration at <code>/usr/local/var/postgres/postgresql.conf</code> had the datetype as the international format of <code>dmy</code>

Changing datetype to the American format of <code>mdy</code> fixed this issue for me.

blocks|key|169951|text|我也有这个问题。我发现这是我的问题。这意味着当我在没有指定表列情况下使用关联进行查询时。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169952|class+Holiday+<+ApplicationRecord
+++++belongs_to+:company
end

class+Company+<+ApplicationRecord
++++has_many+:timeoffs
end|code-block|syntax|javascript|169953|在假日模型中我查询|169954|company.timeoffs.where("(start_date+<=+?+and+end_date+>=+?)+and+id+!=+?",+begin_date,+begin_date,+1)|169955|出现该错误的原因是，在将代码更改为后，我没有指定它适用于哪个表的id|offset|length|style|CODE|169956|company.timeoffs.where("(start_date+<=+?+and+end_date+>=+?)+and+time_offs.id+!=+?",+begin_date,+begin_date,+1)|169957|entityMap^0|0|0|0|0|W|2|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I got that problem. 
And I found out that it was my query.
It mean when I query with association without specifying a table column.
ex:

<pre><code>class Holiday &lt; ApplicationRecord
 belongs_to :company
end

class Company &lt; ApplicationRecord
 has_many :timeoffs
end
</code></pre>

In Holiday model I query

<pre><code>company.timeoffs.where("(start_date &lt;= ? and end_date &gt;= ?) and id != ?", begin_date, begin_date, 1)
</code></pre>

The error occurs because I didn't specify which table's <code>id</code> 
It worked for me after I changed the code to

<pre><code>company.timeoffs.where("(start_date &lt;= ? and end_date &gt;= ?) and time_offs.id != ?", begin_date, begin_date, 1)
</code></pre>

I am trying to create an ActiveRecord Object.But I'm getting this error while creating it.

<pre><code>(0.1ms) ROLLBACK
ActiveRecord::StatementInvalid: PG::InFailedSqlTransaction: ERROR: current transaction is aborted, commands ignored until end of transaction block
</code></pre>

Any ideas folks regarding the issue.

ActiveRecord::StatementInvalid: PG InFailedSqlTransaction

PostgreSQL

数据库

我正在尝试创建ActiveRecord Object.But，创建时遇到此错误。(0.1ms)  ROLLBACKActiveRecord::StatementInvalid: PG::InFailedSqlTransaction: ERROR:  current transaction is       aborte...

问ActiveRecord：：StatementInvalid无效: PG InFailedSqlTransaction
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ActiveRecord：：StatementInvalid无效: PG InFailedSqlTransactionEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ActiveRecord：：StatementInvalid无效: PG InFailedSqlTransaction
EN