> Now that I think about it, this could happen to us as well. We have peer review for each database change, but only at the source level (so, definition of the

> Now that I think about it, this could happen to us as well. We have peer review for each database change, but only at the source level (so, definition of the schema); the actual commands for schema changes are usually generated automatically. If you're using any of the DBIx::Class deployment tools they should be perfectly happy writing the DDL to disk and then running it from there, specifically to make it possible to audit the DDL as part of the commit that changed the result classes. Generated != unauditable, especially when the tools are trying their best to co-operate :D