Description: ------------ One of the things which is really neat in PHPUnit is the ability to log a run into a database. Scenario: An organization runs unit tests, documentation, etc nightly. They wish to provide an easily queried set of data about coding style / standards - this enables them to examine it in the same tool as other logged data. The codebase is significant, and makes the use of XML hard to scale (performance).

I'm of the opinion that PHP_CodeSniffer is a report tool, not a query tool. With that in mind, you might be best generating the report in XML, then parse that to gather the data to put into the database. However, this wouldn't improve performance only hinder it.

I don't think this will ever be built. PHPCS integrates into build systems and I see this sort of reporting as being the job of the build system itself. If you are already custom coding a build system, I don't think it's that much effort to pump XML-based output into the DB after parsing.