That's a bug in 1.1.4 which is fixed in git. If you grab the latest
you should be OK.
On Wed, Jul 23, 2008 at 11:16 AM, Jonathan Leighton
<[EMAIL PROTECTED]> wrote:
> I have been upgrading my helper specs due to the recent change regarding
> mixing in modules:
> http://blog.davidchelimsky.net/2008
I have been upgrading my helper specs due to the recent change regarding
mixing in modules:
http://blog.davidchelimsky.net/2008/5/29/rspec-waving-bye-bye-to-implicit-module-inclusion
Unfortunately I have hit a snag. It seems that when the helper uses
routes I get an error about a nil object. For i
fashion in china
Attachments:
http://www.ruby-forum.com/attachment/2442/599260225417414177.jpg
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Sorry, hit the tab and enter key too soon :)
You'd stub out the model.
class DummyModel
acts_as_curseable
end
it "should ask the database to set up a transaction" do
DummyModel.connection.should_receive("BEGIN;").once
... then the execution code to make that happen
end
it "should ask the
On Mon, Jul 21, 2008 at 6:38 PM, Keith McDonnell <[EMAIL PROTECTED]> wrote:
> I /could/ use an SQL cursor but:
> I don't know if these are valid reasons however :)
The only thing you gain with a direct SQL cursor is the guarantee of
hitting each row exactly once without having to pull down all the
