>I'm having a Catch 22 problem and I'm thinking of a best way to handle it, may be you can suggest something.
>
>In my test class we have rollback property set to true and it automatically rolls back all SQL commands.
>
>This is good as I don't want my tests to create new rows in the database.
>
>Unfortunately, for the particular case I have right now I first create parent row and then in a separate method and separate command try to create a child row.
>
>Since the original transaction was rolled back, I am getting the Foreign Key violation error and can not really test my procedure.
>
>So, what is the best way to handle this situation - I don't really want to create extra rows, but I don't want to get the SQL error either.

I am having a similar issue myself in about a support I would like to add in a specific application. It is really not clear on the best approach to handle such transactional commands when negotiating with parent-child relationship.