diff options
author | Aaron Patterson <aaron.patterson@gmail.com> | 2013-03-22 19:41:29 -0700 |
---|---|---|
committer | Aaron Patterson <aaron.patterson@gmail.com> | 2013-03-22 19:41:29 -0700 |
commit | 7a872e9d84be2f0205d8ca811698be92195ef0e1 (patch) | |
tree | faceaaedddf84672e014617c57f3698672cacc70 /activerecord/CHANGELOG.md | |
parent | db3a6e6a7fc80e85afe239abf5d01aa30685c1c1 (diff) | |
parent | bc8ebefe9825dbff2cffa29ff015a1e7a31f9812 (diff) | |
download | rails-7a872e9d84be2f0205d8ca811698be92195ef0e1.tar.gz rails-7a872e9d84be2f0205d8ca811698be92195ef0e1.tar.bz2 rails-7a872e9d84be2f0205d8ca811698be92195ef0e1.zip |
Merge branch 'schema'
* schema:
add uuid primary key support
separate primary key from column type
push the mysql add_column up to the abstract adapter
allow multiple add columns
pull add_column_options! off the pg connection class
add a pg visitor for dealing with schema modification
push alter table add column sql in to the schema modification visitor
there is no reason to check for an already defined column
push column initialization down to the factory method
@columns list is no longer necessary
keep ivars private, do not manipulate them outside their owner object
factory methods should not alter object state
push SQL generation inside the schema creation object
mostly decouple TableDefinition from the database connection
remove to_sql from TableDefinition
decouple column definition from the database connection
stop depending on sql_type in pg
remove knowledge of SQL from the column definition object
Diffstat (limited to 'activerecord/CHANGELOG.md')
0 files changed, 0 insertions, 0 deletions