# SQLite version 3.x
#   gem install sqlite3
#
#   Ensure the SQLite 3 gem is defined in your Gemfile
#   gem 'sqlite3'
#
default_sqlite: &default_sqlite
  adapter: sqlite3
  pool: 5
  timeout: 5000

development:
  <<: *default_sqlite
  database: db/development.sqlite3

# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
  <<: *default_sqlite
  database: db/test.sqlite3

default_postgres: &default_postgres
  adapter: postgresql
  encoding: unicode
  pool: 5
  username: <%= ENV["DB_USERNAME"] %>
  password: <%= ENV["DB_PASSWORD"] %>
  
production:
  <<: *default_postgres
  database: geghard_PRODUCTION

staging:
  <<: *default_postgres
  database: geghard_STAGING
  
# SQLite version 3.x
#   gem install sqlite3
#
#   Ensure the SQLite 3 gem is defined in your Gemfile
#   gem 'sqlite3'
#
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.

default_postgres: &default_postgres
  adapter: postgresql
  encoding: unicode
  pool: 5
  username: <%= ENV["DB_USERNAME"] %>
  password: <%= ENV["DB_PASSWORD"] %>

development_postgres: &development_postgres
  <<: *default_postgres
  host: localhost
  username: postgres
  password: password
  
production:
  <<: *default_postgres
  database: geghard_PRODUCTION

staging:
  <<: *default_postgres
  database: geghard_STAGING

development:
  <<: *development_postgres
  database: geghard_DEVELOPMENT

test:
  <<: *development_postgres
  database: geghard_TEST
  

Reconfigure so that we can use PGSQL in all envs
Reconfigure so that we can use PGSQL in all envs

We will start using the XML and JSON types that are PG-specific. This
forces us to stop using SQLite in dev/test.
