Great !<br>As always thanks!<br><br>Cheers!<br>sinclair<br><br><div class="gmail_quote">On Nov 29, 2007 12:12 PM, David Chelimsky <<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Nov 29, 2007 11:06 AM, David Chelimsky <<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>> wrote:<br>> On Nov 29, 2007 10:55 AM, sinclair bain <<a href="mailto:rspec.user@gmail.com">
rspec.user@gmail.com</a>> wrote:<br>> > Hey,I just updated from the edge and it looks like this _issue_ has<br>> > resurfaced.<br>> ><br>> > Yesterday things were working (stories and specs).<br>
> > No code base changes, only rspec and rspec_on_rails<br>> ><br>> > After updating today I now need to set <config.txn...fixtures> to false in<br>> > the spec_helper.rb<br>> > to get the specs running, the stories are fine. Looks like the fixture
<br>> > loading is trying to start a txn.<br>> ><br>> ><br>> > I will look around a bit more and see.<br>><br>> I'm on it - will have a fix in about 5 minutes.<br><br></div>OK - this is fixed in r3014.
<br><br>Basically, we've been moving some responsibilities around as we<br>improve interoperability w/ Test::Unit. A side effect was that setup<br>was getting called twice. Running the pre_commit task against mysql<br>
didn't show this problem because mysql is happy to run transactions<br>inside transactions.<br><br>Should be all good now.<br><br>Cheers,<br><font color="#888888">David<br></font><div><div></div><div class="Wj3C7c"><br>
><br>><br>> ><br>> ><br>> ><br>> > Cheers!<br>> > sinclair<br>> ><br>> ><br>> ><br>> > On Oct 24, 2007 10:58 PM, Scott Taylor <<a href="mailto:mailing_lists@railsnewbie.com">
mailing_lists@railsnewbie.com</a> ><br>> > wrote:<br>> > ><br>> > > Okay - so the sqlite bug reported a day or so ago on the list is real<br>> > > bug. I'm going to file something in the tracker for that...
<br>> > ><br>> > > I also learned that before(:all)...after(:all) is not wrapped in a<br>> > > transaction, the way before(:each)...after(:each) is. Is there some<br>> > > reason behind this? Can you not wrap transactions inside transactions?
<br>> > ><br>> > > Scott<br>> > ><br>> > > _______________________________________________<br>> > > rspec-users mailing list<br>> > > <a href="mailto:rspec-users@rubyforge.org">
rspec-users@rubyforge.org</a><br>> > > <a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br>> > ><br>> ><br>> >
<br>> ><br>> > --<br>> ><br>> ><br>> > Cheers!<br>> > sinclair<br>> > _______________________________________________<br>> > rspec-users mailing list<br>> > <a href="mailto:rspec-users@rubyforge.org">
rspec-users@rubyforge.org</a><br>> > <a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br>> ><br>><br>_______________________________________________
<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users
</a><br></div></div></blockquote></div><br><br clear="all"><br>-- <br><br><br>Cheers!<br>sinclair