On Feb 23, 8:50 pm, Stefan Lischke <[email protected]> wrote:
> Thats bad, how can i disable this "feature".
> I also need to look at the database when debugging my tests.
>
> Its not a problem for me to pay the cost of reloading the fixtures
> which i do not use.
>
You can turn off transaction fixtures in test_helper.rb or you can
change your transaction isolation level.
Fred
> thanx in advance
>
> schtief
>
> 2009/2/23 Frederick Cheung <[email protected]>:
>
>
>
> > On 23 Feb 2009, at 20:24, schtieF wrote:
>
> >>> Are you checking by looking at the database with whatever command
> >>> line
> >>> tool your db provides ?
> >>> tests run inside a transaction and by default other connections can't
> >>> see uncommitted changes from another transaction.
>
> >> I'm using phpMyAdmin to look at the database used for my tests.
>
> >> That might be a solution, but why does ActiveRecord not commit after
> >> save! ?
> >> that does not make any sense to me.
>
> > Because in tests the entire test is wrapped in a transaction (so that
> > after the test all the changes it made can be rolled back so that
> > fixtures don't have to be reloaded after each test)
>
> > Fred
> >> schtief
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
