rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove unnecessary `connection_name` variable	Ryuta Kamizono	2016-12-06	1	-2/+1
\|
*	Make pg adapter use bigserial for pk by default	Pavel Pravosud	2016-12-05	1	-1/+11
\|
*	For `PostgreSQL >= 9.4` use `gen_random_uuid()`	Yaw Boakye	2016-11-22	1	-0/+8
\| \| \| \| \| \| \| \| \| \|	Since 9.4, PostgreSQL recommends using `pgcrypto`'s `gen_random_uuid()` to generate version 4 UUIDs instead of the functions in the `uuid-ossp` extension. These changes uses the appropriate UUID function depending on the underlying PostgreSQL server's version, while maintaining `uuid_generate_v4()` in older migrations.
*	Avoid to allow unused splat args for `t.timestamps` in `create_table`	Ryuta Kamizono	2016-08-14	1	-2/+2
\| \| \| \| \| \|	Unfortunately `t.timestamps` in `create_table` allows unused splat args. But the same one in `change_table` does not allow them. This commit fixes the inconsistent behavior.
*	normalizes indentation and whitespace across the project	Xavier Noria	2016-08-06	1	-12/+12
\|
*	applies new string literal convention in activerecord/lib	Xavier Noria	2016-08-06	1	-1/+1
\| \| \| \| \|	The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
*	Add migration compatibility class for Rails 5.1	Rafael Mendonça França	2016-05-10	1	-1/+4
\|
*	Migrations: move version-finding responsibility	yui-knk	2016-04-29	1	-0/+10
\| \| \| \| \| \| \|	`ActiveRecord::Migration` needn't know about migration version compatibility lookup. Delegate it to the Compatibility module. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
*	Update compatibility.rb	Bogdan	2016-03-26	1	-1/+1
\|
*	Correctly show deprecation warning for incompatible migrations	Prathamesh Sonpatki	2016-02-12	1	-1/+1
\|
*	Intervene on change_table as well as create_table	Matthew Draper	2016-01-30	1	-0/+13
\|
*	Pare back default `index` option for the migration generator	Prathamesh Sonpatki	2016-01-24	1	-0/+12
\| \| \| \| \| \| \| \| \| \|	- Using `references` or `belongs_to` in migrations will always add index for the referenced column by default, without adding `index:true` option to generated migration file. - Users can opt out of this by passing `index: false`. - Legacy migrations won't be affected by this change. They will continue to run as they were before. - Fixes #18146
*	fix remove_index for postgresql when running legacy migrations	Lachlan Sylvester	2016-01-06	1	-2/+3
\|
*	Support removing custom-names indexes when only specifying column names	Grey Baker	2015-12-15	1	-0/+25
\|
*	Ignore index name in `index_exists?` when not passed a name to check for	Grey Baker	2015-12-15	1	-0/+11
\|
*	In 4.2 migrations, `timestamps` defaulted to `null: true`	Matthew Draper	2015-12-15	1	-0/+24
\| \| \| \| \|	.. it also showed a deprecation warning, but we obviously needn't retain that.
*	Add migration versioning via Migration subclasses	Matthew Draper	2015-12-15	1	-0/+30