Rails - Sep 2005 - DB Constaints and Test Fixtures

I''m trying to write a unit test for a table. The table
has a trigger that throws an exception preventing
deletions. They are not allowed by the business logic.
I can''t run a unit test because fixture can''t tear
down the data.

Is there some way in my unit test I could disable the
trigger during the fixture() execution, but have it
enabled during a unit test to test this behavior?

On top of this, there are two different database
targets, so it needs to do something different
depending on the database type to disable the
triggers.

Shawn


		
__________________________________ 
Yahoo! Mail - PC Magazine Editors'' Choice 2005 
http://mail.yahoo.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 30, 2005, at 4:42 PM, Shawn Garbett wrote:
> Is there some way in my unit test I could disable the
> trigger during the fixture() execution, but have it
> enabled during a unit test to test this behavior?
You could eliminate the problem by using transactional fixtures:

   class FooTest < Test::Unit::TestCase
     self.use_transactional_fixtures = true
     ...
   end

Or turn them on by default in test/test_helper.rb:
   Test::Unit::TestCase.use_transactional_fixtures = true

Fixtures are loaded once at the beginning of the test run and
are restored after each test by doing a transaction rollback.

Best,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDPeC9AQHALep9HFYRAugsAJoDZzjSgE8f3hoa6Cka+j0A+BVrpgCffj/R
0ckMBcg/GPVVvTeGbdEpbo0=EUlQ
-----END PGP SIGNATURE-----