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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Refactor serialized types to be partially defined as custom properties	Sean Griffin	2014-05-29	1	-3/+7
\| \| \| \| \| \| \|	Many of the methods defined in `AttributeMethods::Serialization` can be refactored onto this type as well, but this is a reasonable small step. Removes the `Type` class, and the need for `decorate_columns` to handle serialized types.
*	Ensure we always use instances of the adapter specific column class	Sean Griffin	2014-05-28	1	-1/+1
\| \| \| \| \| \|	- Create a consistent API across adapters for building new columns - Use it for custom properties so we don't get `UndefinedMethodError`s in stuff I'm implementing elsewhere.
*	Maintain column order when overriding existing columns	Sean Griffin	2014-05-28	1	-3/+8
\| \| \| \| \| \|	Working towards re-implementing serialized attributes to use the properties API exposed the need for this, as serializing a column shouldn't change the order of the columns.
*	Merge pull request #15389 from sgrif/sg-property-inheritance	Rafael Mendonça França	2014-05-28	1	-5/+7
\|\ \| \| \| \|	Ensure custom properties work correctly with inheritance
\| *	Ensure custom properties work correctly with inheritance	Sean Griffin	2014-05-28	1	-5/+7
\| \|
* \|	Move types to the top level `ActiveRecord` namespace	Sean Griffin	2014-05-27	1	-1/+1
\|/ \| \| \| \|	`ActiveRecord::ConnectionAdapters::Type::Value` => `ActiveRecord::Type::Value`
*	Remove AR Properties from the public API	Sean Griffin	2014-05-27	1	-14/+2
\| \| \| \| \|	Making this part of the public API was premature, let's make it private again while I continue to work on the surrounding code.
*	Deprecate decimal columns being automatically treated as integers	Sean Griffin	2014-05-27	1	-1/+13
\| \| \| \| \| \|	With ActiveRecord::Properties, we now have a reasonable path for users to continue to keep this behavior if they want it. This is an edge case that has added a lot of complexity to the code base.
*	Add a public API to allow users to specify column types	Sean Griffin	2014-05-26	1	-0/+95
	As a result of all of the refactoring that's been done, it's now possible for us to define a public API to allow users to specify behavior. This is an initial implementation so that I can work off of it in smaller pieces for additional features/refactorings. The current behavior will continue to stay the same, though I'd like to refactor towards the automatic schema detection being built off of this API, and add the ability to opt out of automatic schema detection. Use cases: - We can deprecate a lot of the edge cases around types, now that there is an alternate path for users who wish to maintain the same behavior. - I intend to refactor serialized columns to be built on top of this API. - Gem and library maintainers are able to interact with `ActiveRecord` at a slightly lower level in a more stable way. - Interesting ability to reverse the work flow of adding to the schema. Model can become the single source of truth for the structure. We can compare that to what the database says the schema is, diff them, and generate a migration.