| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Dup'ed ActiveRecord objects may not share the errors object
|
| |
| |
| |
| | |
dup'ed object (call ActiveModel::Validations#initialize_dup). Closes #7291
|
|\ \
| | |
| | | |
Add :platform to redcarpet gem, pointing to :ruby only.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This file is used at least by Active Merchant, its existence
is maybe not necessary but no big deal either.
This reverts commit ae9b3d7cecd77b9ace38671b183e1a360bf632b6.
|
|\ \ \
| | | |
| | | | |
Adding reference a few Time and Date aliases in Rails 4.0 release notes
|
|/ / /
| | |
| | |
| | |
| | | |
I originally contributed these aliases 10 months ago and just never got
it added to the Rails 4.0 release notes. Here they are.
|
| | | |
|
|\ \ \
| | | |
| | | | |
ActiveRecord: sum expression returns string '0' for no records, fixed
|
|/ / / |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Ignore asset url query string or anchor when generating path
|
| | | |
| | | |
| | | |
| | | | |
computing public path
|
| | | |
| | | |
| | | |
| | | | |
allocations
|
|/ / /
| | |
| | |
| | | |
https://bugs.ruby-lang.org/issues/7166
|
|\ \ \
| | | |
| | | | |
Refactor AssetUrlHelper
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Conflicts:
railties/test/application/configuration_test.rb
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Removed useless "extend SanitizeHelper::ClassMethods"
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
Since SanitizeHelper includes ActiveSupport::Concern,
extending of it ClassMethods is no needed.
|
|\ \ \ \
| |/ / /
|/| | | |
Minor cleanup, helper method was only used once
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
refactoring of uniqueness validate_each
|
|/ / /
| | |
| | |
| | | |
get scope_value only one time dependig on reflection
|
|\ \ \
| | | |
| | | | |
Fix typo in inet and cidr saving
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Use 1.9 Hash syntax in railties
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
remove 'then' from conditional statement
|
|/ / / / |
|
|\| | |
| | | |
| | | |
| | | |
| | | | |
arturopie/7914-defaults-on-domains-and-multiple-schemas
Fixes #7914 - PostgreSQL adapter doesn't fetch column defaults when using multiple schemas and domains
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove parsing of character type default values for 8.1 formatting since
Rails doesn't support postgreSQL 8.1 anymore.
Remove misleading comment unrelated to code.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
According to postgreSQL documentation:
(http://www.postgresql.org/docs/8.2/static/catalog-pg-attrdef.html)
we should not be using 'adsrc' field because this field is unaware of
outside changes that could affect the way that default values are
represented. Thus, I changed the queries to use
"pg_get_expr(adbin, adrelid)" instead of the historical "adsrc" field.
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
PostgreSQL adapter properly parses default values when using multiple
schemas and domains.
When using domains across schemas, PostgresSQL prefixes the type of the
default value with the name of the schema where that type (or domain) is.
For example, this query:
```
SELECT a.attname, d.adsrc
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = "defaults"'::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum;
```
could return something like "'<default_value>'::pg_catalog.text" or
"(''<default_value>'::pg_catalog.text)::text" for the text columns with
defaults.
I modified the regexp used to parse this value so that it ignores
anything between ':: and \b(?:character varying|bpchar|text), and it
allows to have optional parens like in the above second example.
|
|\ \ \
| | | |
| | | | |
Clean up Gemfile entry (replace double quotes with single quotes) [ci skip]
|
|/ / / |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
queues in the classes that use them instead.
|
|\ \ \
| | | |
| | | | |
Prompt to run rake when accidentally typed rails
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Developers from all levels will accidentally run rake tasks using the `rails` keyword when they meant to use `rake`. Often times beginners struggle with the difference between the tools. The most common example would be `$ rails db:migrate`
Rather than telling the developer simply that they did not use a valid rails command, we can see if it was a valid rake command first. If it is a valid rake command we can auto execute it giving the user a period of time to cancel if that isn't what they intended.
Here is what `rake db:migrate` would look like if you cancel the command:
```sh
$ rails db:migrate
Assuming you meant: $ rake db:migrate
press any key to cancel in 3 seconds
>
command terminated ...
```
Here is what it looks like if you don't cancel the command:
```sh
$ rails db:migrate
Assuming you meant: $ rake db:migrate
press any key to cancel in 3 seconds
>
Running: $ rake db:migrate
== Foo: migrating ============================================================
== Foo: migrated (0.0000s) ===================================================
```
|