If a PRIMARY KEY field is defined in sqlite without autoincrement then
keys might be reused when rows are deleted, explicitly settings autoincrement
will prevent this.

Autoincrement is not enabled by default due to additional overhead introduced
with autoincrement bookkeeping and should only be enabled when the additional
uniqueness is required.

fixes #1339
closes #921

* 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)

[2.0] DDC-313 - Removed abstracted trigger support, list functions, list users and the platform specific code to generate the queries for this stuff.

[2.0] DDC-312 -  Refactored View support of all platforms a little - Oracle now also supports the retrieval of the sql used to generate a view so that a common datastructure View is a viable option.