initial import (based on https://github.com/opscode-cookbooks/database)
Verify and update password if user already exists
Replace README with the standard template file
Basics for the WebUI part of the barclamp
Display MySQL specific settings only when MySQL is selected
allow multiple database proposals
Skeletons for client and server recipes
Generate random passwords if nothing was set in the proposal
Copy database/<sql_engine> role attributes to <sql_engine>

By doing this we can just use the postgresql/mysql cookbooks from the original
postgresql-/mysql-barclamps without changing all the attribute names.
imported mysql, postgresql and openssl cookbooks from the respecitive barclamps
Install rubygem "pg" from RPM on SUSE
remove database resource/provider from mysql and postgresql cookbooks

they conflict with the ones from the "database" barclamp
pg_hba.conf: write subnet+netmask instead of subnet+subnet
postgresql: fixed test for a working login:

connect to the address we told the server to listen on, not to
localhost
postgresql: fix 'database "db_maker" does not exist'

change password if role exists
Fixed mysql package list for SUSE
mysql: SUSE related changes
Added missing data_bags directory
Share the "db_maker_password" attribute between postgresql and mysql
python-client recipes and Database::Utils Library

Use postgresql/mysql::python-client to install the correct python bindings for the
selected database backend.

The methods in the Database::Utils Library provide help to set the correct
Parameters for the database and database_user resources, depending on the
selected database backend.