I'm looking for the answer to this question, came across this blog entry It suggests to declare inside the describe block describe "xxx" do self. Use_transactional_fixtures = false I tried it with Rails 3.0.7 with RSpec 2.6.3, and looks like working.
I'm looking for the answer to this question, came across this blog entry It suggests to declare inside the describe block describe "xxx" do self. Use_transactional_fixtures = false ... I tried it with Rails 3.0.7 with RSpec 2.6.3, and looks like working.
RSpec. Configure do |config| config. Use_transactional_fixtures = true end.
This didn't work. I put this in the before(:all) and it doesn't seem to work. I'm still getting this error which is typically solved by turning off transactional fixtures for the test.
PGError: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query – Nicolo77 Oct 13 '10 at 16:51 1 You should put this code outside any :all or describe block. The spec_helper. Rb file is a good place if you wanna set this globally.
And I think David meant to say false instead of true. – Lailson Bandeira Oct 14 '10 at 2:11.
You can disable transactional fixtures globally by putting config. Use_transactional_fixtures = false on the spec_helper.rb. If you want to control them by test (e.g. Use transactional just on some of them), you can set this behavior with DatabaseCleaner.
I've had a related problem when testing pages with javascript on the browser (a scenario that does not work with transactional fixtures). Here's how I managed to work around it: github.com/lailsonbm/contact_manager_app.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.