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

	Commit message (Collapse)	Author	Age	Files	Lines
*	use correct Gemfile in `bin/setup` test	yuuji.yaginuma	2016-09-11	1	-0/+18
\| \| \| \| \| \| \|	Currently, `bin/setup` test uses Gemfile of Rails. But this Gemfile is not a file to be used in Rails application. Add a Gemfile to Rails application that is created for test, it has been modified to use the Gemfile.
*	applies new string literal convention in railties/test	Xavier Noria	2016-08-06	1	-4/+4
\| \| \| \| \|	The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
*	Added notice when a database is successfully created or dropped.	bogdanvlviv	2016-04-17	1	-0/+2
\|
*	Shorten ActiveRecord::InternalMetadata.table_name to ar_internal_metadata	Yasuo Honda	2016-02-01	1	-1/+1
\| \| \| \|	to support Oracle database which only supports 30 byte identifier length
*	rake log:clear task updated refs[#22544]	Pramod	2016-01-09	1	-3/+3
\| \| \| \| \| \| \| \|	- Avoided truncating all files if no ENV['LOGS'] specified - Updated task to accept LOGS=all for truncating all files from log/ i.e. log/*log - If no LOGS specified will truncates standard environment log files i.e. 'development,test,production' - CHANGELOG & guide update added - bin/setup test cases fixed
*	Fixing tests and re-locating error checking.	schneems	2016-01-08	1	-1/+1
\|
*	Prevent destructive action on production database	schneems	2016-01-07	1	-1/+1
\| \| \| \| \| \| \|	This PR introduces a key/value type store to Active Record that can be used for storing internal values. It is an alternative implementation to #21237 cc @sgrif @matthewd. It is possible to run your tests against your production database by accident right now. While infrequently, but as an anecdotal data point, Heroku receives a non-trivial number of requests for a database restore due to this happening. In these cases the loss can be large. To prevent against running tests against production we can store the "environment" version that was used when migrating the database in a new internal table. Before executing tests we can see if the database is a listed in `protected_environments` and abort. There is a manual escape valve to force this check from happening with environment variable `DISABLE_DATABASE_ENVIRONMENT_CHECK=1`.
*	add test coverage for `bin/setup`.	Yves Senn	2015-05-06	1	-0/+54
	Make sure this script keeps working and has consistent output.