schneems 5b96027ef6 Allow "url" sub key in database.yml configuration ... Currently a developer can pass in a YAML configuration that fully specifies connection information: ``` production: database: triage_production adapter: password pool: 5 ``` They can also pass in a string that specifies a connection URL directly to an environment key: ``` production: postgresql://localhost/foo ``` This PR allows the use of both a connection url and specifying connection attributes via YAML through the use of the "url" sub key: ``` production: url: postgresql://localhost/foo pool: 3 ``` This will allow developers to inherit Active Record options such as `pool` from `&defaults` and still use a secure connection url such as `<%= ENV['DATABASE_URL'] %>`. The URL is expanded into a hash and then merged back into the YAML hash. If there are any conflicts, the values from the connection URL are preferred. Talked this over with @josevalim		2013-12-30 12:21:14 -05:00
..
active_record/connection_adapters	Ensure disconnecting or reconnecting resets the transaction state	2012-09-15 00:03:04 +01:00
assets	Added test to illustrate bad binary blobs.	2012-01-31 13:45:00 -06:00
cases	Allow "url" sub key in database.yml configuration	2013-12-30 12:21:14 -05:00
fixtures	Extend ActiveRecord::Base#cache_key to take an optional list of timestamp attributes of which the highest will be used.	2013-11-02 16:05:19 -07:00
migrations	Preserve magic comments and content encoding of copied migrations.	2013-03-09 15:38:02 +09:00
models	make sure cached table name is a string. fixes #12582	2013-12-12 10:47:07 -08:00
schema	extract PG range tests from datatype_test.rb into range_test.rb	2013-12-13 14:17:21 +01:00
support	Deprecate use of string in establish_connection as connection lookup	2013-12-24 10:18:54 +01:00
.gitignore
config.example.yml	Simulated & actual (manual/skipped) PostgreSQL auto-reconnection tests.	2012-07-16 09:55:20 -07:00
config.rb