- the code is "in the process of" getting a cleanup.  there are still a
  few globally scoped variables that ought to be removed and/or replaced
  by local scoped variables.

- testing various corner cases:
  - errors dumping during upgrade
  - errors dumping during purge

- multiple instance support for many databases from one package.  the
  idea is to create seperate "package configurations" that are derived
  from the main configuration, using something to keep them in a namespace
  that won't conflict with the standard package configurations.  something
  like /etc/dbconfig-common/package_instance.conf etc.  most of dbconfig's
  code could escape needing a rewrite then, as we could internally "trick"
  the code into thinking that was the actual package name.

- provide a normal-user-accessible script for setting up databases
  (for running out of public_html type directories etc).

- think about how this should tie in with the webapps-common.

- begin discussion on having the "best-practices" document incorporated
  in some form as debian policy.

- ask if the user is to be completely deleted or only have privileges
  revoked in mysql.  this is the default in pgsql, but in pgsql the drop
  will fail if the user owns other databases (not so in mysql).
  See bug #400566

- mysql does not support ssl for the time being (see bug #291945) <- fixed...

- FIX no-admin patch to use new VAR instead of debconf item (to prevent
   regression test from failing)

*  Fix postinst to use _dbc_asuser when appropriate   
   
*  Add testcase that tests admin remove scripts (#705222)

*  debconf is not a registry should not lead to dbconfig-common has its own
   registry (which is currently the case)

*  Provide config parsers (as requested in 690390(?) against debconf)

*  Get dbconfig-common mentioned in policy

*  Remove some of the upgrade code if no package depends on it make things easier

*  More databases (e.g. mongodb)

*  Support DSN: apparently python has multiple ways of making the connection

*  Investigate if ENCODING is done properly, maybe needs more care:
   http://www.postgresql.org/docs/current/static/multibyte.html

*  Fix unittest framework for posh, now a "mock" version breaks the "real"
   version with:
   "mock-mysql-tests.sh: mysql: can't find function definition file."
   No idea why pgsql works though.

*  Add pgsql upgrade example package to test that as well

*  fix bug 808370 by resetting properly when dbc_command = reconfigure

*  Check if postgresql users are limited to dbc_dballow (doesn't look like it)

*  Check if PostgreSQL users are limited to their own database (doesn't look
   like it)

*  Add documentation for packages on changing the default for backups

*  Investigate which databases could/should be supported (list from adodb site):
    Access
    ADO
    CSV
    Firebird
    Frontbase
    IBM DB2
    Informix
    Interbase
    LDAP
    Microsoft SQL Server
    MySQL
    Netezza
    ODBC
    ODBTP
    Oracle
    PDO
    Postgresql
    SAP ADS
    SAP ASE
    SAP Maxdb
    SAP Sqlanywhere
    Sqlite
    Sybase
    Plain Text
    Visual Foxpro
