| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default when creating a project with `--database=postgresql` the `config/database.yml` file that is generated has a user specified that is the same as the app name
```
development:
adapter: postgresql
encoding: unicode
database: <%= app_name %>_development
pool: 5
username: <%= app_name %>
password:
```
This is counterintuitive and would rarely be valid. By default postgres creates a user with the current user name (http://www.postgresql.org/docs/9.3/static/database-roles.html) "it will have the same name as the operating system user that initialized the database cluster":
```
$ whoami
schneems
```
If the `username` is left out postgresql will assume that you wish to log in as the default user
```
$ psql -c '\du'
List of roles
Role name | Attributes | Member of
-----------+------------------------------------------------+-----------
schneems | Superuser, Create role, Create DB, Replication | {}
```
A good sensible default then for auto generated `database.yml` files is to remove the `username`, and have postgres attempt to connect to the database as the currently logged in user.
Instead of submitting with a blank password, don't submit a password.
|
| |
|
|
| |
[ci skip]
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit 293a1a68992ba3e3e80f9f0f685e866ff79bf11a.
|
| |
|
|
| |
Example code does not run yet with beta1.
|
| |\
| |
| | |
Remove <tt> tag in 4_1_release notes. [ci skip].
|
| | | |
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| | |
This reverts commit 41ba51f4850a8cd2fe69789011ac33366366d32f.
[ci skip]
|
| | |
| |
| |
| |
| |
| | |
This reverts commit f4804fafecdc057988575b4516afe9ca1d5f42fc.
[ci skip]
|
| | |
| |
| |
| |
| |
| | |
This reverts commit 427db6b9d2b35a72f3c017eb19a2e1e800b0a7a3.
[ci skip]
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit b58f3a641795e1777aa3e12a853c34ff512acfb9.
Reason: Discussion in https://github.com/rails/docrails/commit/b58f3a641795e1777aa3e12a853c34ff512acfb9
[ci skip]
|
| | |
| |
| |
| |
| | |
The flag will be used in multiple places to check for errors during runtime if enabled.
Source: https://github.com/rails/sprockets-rails/pull/100
|
| | |\ |
|
| | | |\ |
|
| | | |\ \ |
|
| | | | | | |
|
| | | |_|/
| |/| | |
|
| | | | |
| | | |
| | | |
| | | | |
As a side not, the period after etc is not always
needed http://en.wiktionary.org/wiki/etc
|
| | | | | |
|
| | | | |
| | | |
| | | | |
Escape hyphen
|
| | | | |
| | | |
| | | | |
Add escape character for correct rendering
|
| | | | |
| | | |
| | | | |
Use markdown formatting instead
|
| | | | | |
|
| | | | |
| | | |
| | | | |
In the absence of proper escaping the first link was getting messed up and remaining part of the sentence (2nd link) was not displayed in the rendered markdown on the website though it was displaying correctly in the repository markdown file.
|
| | | | |
| | | |
| | | | |
From (svenfuchs/globalize3) to (globalize/globalize)
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Fixed configurable.rb regular expression name check
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
[ci skip] Remove <tt> tag in 4_1_release notes.
|
| |/ / / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Prevent creation of instance methods when `instance_reader = false`, Grammar checks, Conditional statements combined
|
| | | | | |
| | | | |
| | | | |
| | | | | |
checks, Conditional statements combined
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
modified regex for finding table_name from a multiline sql query in postgresql
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously, executing an insert SQL in PostgreSQL with a command like this:
insert into articles(
number)
values(
5152
)
would not work because the adapter was unable to extract the correct articles table name.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #9625
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change most tests to make use of assert_raise returning the raised
exception rather than relying on a combination of flunk + rescue to
check for exception types/messages.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In Minitest, the second argument of assert_raise(s) accepts a string as
the message that should be shown in case of a failure in the assertion
(eg nothing was raised when it should), and not the exception message to
be matched.
To do that we need to save the exception returned from assert_raise(s)
into a local variable and check for the exception message using it.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add information about 'available_locales' and 'enforce_available_locales'
to the configuring guide.
Closes #13202. [ci skip]
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix PostgreSQL range tests on fresh DB
Correcting the name of the table we're creating is self-explanatory.
But we must also move away from the low IDs, because we're not touching the freshly-created primary key sequence; when the time comes, @new_range will be assigned an ID of 1.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The changes in c4044b2 meant the tests would error on a fresh DB.
|
| | |_|/ / / /
|/| | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
fix typos and grammar mistake [ci skip]
|
| | | | | | | | |
|
