These are internal, automatically-created and shouldn't be considered part of
the schema. They cannot be recreated because of their reserved names.

* The old implementation produced invalid SQLite statements for tables with
  a composite primary key, as SQLite cannot have more than one primary key
  clause and autoincrement can only be declared on a single column
* There is currently no way to tell from its pragma if an SQLite column
  auto-increments, therefore enabling it on all primary keys is not accurate
* SQLite primary keys auto-increment anyway (but slightly differently from an
  actual auto-increment column -- not guaranteed unique)

This enables a more natural way of interacting with result sets,
and re-introduces in Doctrine DBAL a feature that has been available
in PDO from the begining.

DDC-217 - Refactor result caching to use a value object for all the important information which simplifies the code considerably and makes caching more powerful.

DDC-217 - Refactor result cache again to be much simpler, previous approach was too complicated and something like this needs longer testing. Now only caching the full result.