-
Notifications
You must be signed in to change notification settings - Fork 81
Support running without database.yml #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support running without database.yml #78
Conversation
Two minor changes to configuration_spec: - replaced adapter_name with adaptername in dummy environments; underscore is not valid in URL schema - URLencoded commas in search_path
WHY are we even supporting 1.8 anymore? ;( |
Hi @dividedmind, what an awesome work! About Ruby 1.8 support, I agree we could drop it, the idea was to keep it for as long as it's not too much of a burden or require too much additional code. I wonder how much people rely on this support though... What about creating an issue and asking for feedback about dropping it? |
end | ||
|
||
# allow easier access | ||
def method_missing(key, *a) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you can implement the other part of this: respond_to_missing?
?
Just an issue would be too easily overlooked; how do you like the approach in #80 ? |
Sometimes stuff (eg. search path) is set from elsewhere. But a config with no adapter nor url is unlikely to be valid. Note this is purely cosmetic change: it would fail either way, but this allows for a better error message.
Support running without database.yml
Added support for running with only DATABASE_URL for 12 factor compliance.
Also refactored the database configuration code.