Re^2: Automated testing of database classes

[MrCromeDome]

The tranasction savepoints sound interesting . While never having investigated them, I'm imagining that SQL Server (the DBMS I'm stuck with) must have some similar functionality. My original suite of tests was very brute force - add rows that I need for my tests, run the tests, manually delete those rows. On the plus side, I at least verified that the delete functionality in Class::DBI worked as intended ;)

Up to this point, I've always verified my database tests using Class::DBI, but I think I like using yet another tool to verify my test data. Looks like Test::DatabaseRow will fit that bill nicely. Thanks for the recommendation!

MrCromeDome

[jplindstrom]

I can imagine that Sybase and MS SQL Server have identical transaction semantics.

This only works if you can do it consistently, but here is how to nest transactions and limit the rollback scope so that it matches that of e.g. a procedure:

    begin tran
    save tran the_procedure_name
    
    --modify stuff

    if ... error ... begin
        rollback tran the_procedure_name
        commit tran
        return 1
    end
 
    --success   
 
    commit tran
    
    return 0

You start with beginning a transaction and immediately saving the transaction to a named savepoint. I've asked around and this doesn't seem to incur very much overhead.

If everything works okay, just commit once to end the outermost transaction.

If anything goes wrong, first rollback to the named savepoint, then commit the transaction (to make sure it's nested properly).

/J