Debugging with uncommitted data

[Norman Njeim]

Can I get PL/SQL Developer to work on non-committed data?

W have an application connecting with an ODBC data source that inputs data in an oracle table, and - before committing this data - calls a stored procedure that reads this data and performs some calculations; after that we have the option of committing the data or roll it back.

In some cases, the procedure is failing and we
are wondering if there's a way to be able to debug uncommitted data (PL/SQL can not see the uncommitted data) . Is there a falg or setting somewhere in PL/SQL Developer that allow us to do that? Thanks!

 

[Marco Kalter]

You can debug with uncommitted data, but you must performs these inserts/updates/deletes as the first step in your Test Scrit. You can execute a rollback at the end of the script if necessary.

You cannot access the uncommitted data from another session in an Oracle database.

 

[ScottMattes]

Maybe if you create a Stored Procedure using AUTONOMOUS TRANSACTION (hope I spelled that correctly) that inserts debug info into a debug table and commits that. You have the code you wish to debug call this SP at various places and then you can look in the debug table to see what is happening.

I have a package that I wrote that uses this idea, plus it lets me record what procedure/function that I am in, etc. It isn't generic enough to use 'out of the box', but it might be a starting point.