Lisa Ugray 52e050ed00 Change sqlite3 boolean serialization to use 1 and 0 ... Abstract boolean serialization has been using 't' and 'f', with MySQL overriding that to use 1 and 0. This has the advantage that SQLite natively recognizes 1 and 0 as true and false, but does not natively recognize 't' and 'f'. This change in serialization requires a migration of stored boolean data for SQLite databases, so it's implemented behind a configuration flag whose default false value is deprecated. The flag itself can be deprecated in a future version of Rails. While loaded models will give the correct result for boolean columns without migrating old data, where() clauses will interact incorrectly with old data. While working in this area, also change the abstract adapter to use `"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for unquoted. These are supported by PostreSQL, and MySQL remains overriden.		2017-07-11 14:52:46 -04:00
..
bootstrap.rb	[Railties] require => require_relative	2017-07-01 18:35:43 +09:00
configuration.rb	Change sqlite3 boolean serialization to use 1 and 0	2017-07-11 14:52:46 -04:00
default_middleware_stack.rb	Remove unnecessary tap call on ActionDispatch::MiddlewareStack instance	2017-06-24 18:46:31 +03:00
finisher.rb	Fully initialize routes before the first request is handled	2017-01-18 11:10:52 +01:00
routes_reloader.rb	Fully initialize routes before the first request is handled	2017-01-18 11:10:52 +01:00