Presumably, you have a development environment that you're working with. Does the database you're using provide any sort of "update logs"? The company I work for uses MySQL's binary logs and query logs in our Sarbanes-Oxley compliance. The former logs anything that changes data while the latter logs pretty much everything. If the DB you're using does provide something like this, you could just pull all the relevant SQLs from the log files that were generated when you ran tests against your development server (you'd probably only be interested in the binary logs) and hand that off to the DBA for perusal.

Update: I was just looking at the DBI_TRACE documentation and you can send all trace information to a file (i.e. DBI->trace(1,"/path/to/log/file")). It should be possible then to parse that file for any update statements your application executed althought it would take quite a bit of regex hackery.