| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | nodoc AR::Generators [ci skip] | Francesco Rodriguez | 2012-10-20 | 4 | -10/+10 |
| | | |||||
| * | Remove mass assignment security from ActiveRecord | Guillermo Iguaran | 2012-09-16 | 1 | -5/+0 |
| | | |||||
| * | add mini-validator on creating migration | Jan Bernacki | 2012-09-06 | 1 | -0/+9 |
| | | | | | move validation to AR | ||||
| * | Extract ActiveRecord::SessionStore from Rails | Prem Sichanugrist | 2012-08-24 | 2 | -36/+0 |
| | | | | | | This functionality will be available from gem `active_record-session_store` instead. | ||||
| * | removes usage of Object#in? from the code base (the method remains defined ↵ | Xavier Noria | 2012-08-06 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case. | ||||
| * | load active_support/core_ext/object/inclusion in active_support/rails | Xavier Noria | 2012-08-02 | 1 | -1/+0 |
| | | |||||
| * | Add fkey attributes to `join_table` migration generator | Aleksey Magusev | 2012-07-19 | 1 | -2/+10 |
| | | |||||
| * | Add join table migration generator | Aleksey Magusev | 2012-07-18 | 2 | -6/+27 |
| | | | | | | | | | | | | | | For instance, running rails g migration CreateMediaJoinTable artists musics:uniq will create a migration with create_join_table :artists, :musics do |t| # t.index [:artist_id, :music_id] t.index [:music_id, :artist_id], unique: true end | ||||
| * | Add references statements to migration generator | Aleksey Magusev | 2012-07-08 | 1 | -4/+16 |
| | | | | | | | | | | | | | | AddXXXToYYY/RemoveXXXFromYYY migrations are produced with references statements, for instance rails g migration AddReferencesToProducts user:references supplier:references{polymorphic} will generate the migration with: add_reference :products, :user, index: true add_reference :products, :supplier, polymorphic: true, index: true | ||||
| * | Fixed generating namespaced table_name_prefix in engines | Wojciech Wnętrzak | 2012-07-06 | 1 | -1/+1 |
| | | |||||
| * | Add polymorphic option to model generator | Aleksey Magusev | 2012-06-27 | 1 | -1/+1 |
| | | | | | | | | | | | For instance, $ rails g model Product supplier:references{polymorphic} generate model with `belongs_to :supplier, polymorphic: true` association and appropriate migration. Also fix model_generator_test.rb#L196 and #L201 | ||||
| * | Refactor migration generator | Oscar Del Ben | 2012-05-18 | 1 | -6/+3 |
| | | |||||
| * | Automatically create indexes for references/belongs_to statements in migrations. | Joshua Wood | 2012-04-14 | 1 | -1/+2 |
| | | |||||
| * | Fix indenting in migration generator | Colin Bartlett | 2012-03-27 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | $ rails generate migration remove_foo_from_bars foo:string This currently generates: def up remove_column :bars, :foo end Fix it: def up remove_column :bars, :foo end | ||||
| * | Avoid another blank line in generated migration and remove assertion as per ↵ | Marcelo Silveira | 2012-03-21 | 1 | -1/+1 |
| | | | | | @spastorino request | ||||
| * | Merge pull request #5532 from mhfs/migration_blank_line | José Valim | 2012-03-21 | 1 | -1/+1 |
| |\ | | | | | Remove blank line from generated migration | ||||
| | * | Remove blank line from generated migration | Marcelo Silveira | 2012-03-20 | 1 | -1/+1 |
| | | | |||||
| * | | Generate Migration Thats Adds Removed Index | Travis Jeffery | 2012-03-21 | 1 | -0/+3 |
| |/ | | | | | When generating a migration that removes a field with an index, the down will add both the field and its index. | ||||
| * | Whitelist all attribute assignment by default. | Michael Koziarski | 2012-03-05 | 2 | -0/+9 |
| | | | | | Change the default for newly generated applications to whitelist all attribute assignment. Also update the generated model classes so users are reminded of the importance of attr_accessible. | ||||
| * | Remove unused implementation of next_migration_number | Marcelo Silveira | 2012-02-23 | 2 | -17/+0 |
| | | |||||
| * | Tidy up migration types. | José Valim | 2011-12-24 | 4 | -11/+10 |
| | | |||||
| * | added ability to specify from cli when generating a model/migration whether ↵ | Dmitrii Samoilov | 2011-12-24 | 4 | -7/+16 |
| | | | | | particular property should be an index like this 'rails g model person name:string:index profile:string' | ||||
| * | Use change in place of up and down in sessions table migration | Vijay Dev | 2011-05-28 | 1 | -5/+1 |
| | | |||||
| * | for => each in model migration template | Guillermo Iguaran | 2011-05-20 | 1 | -1/+1 |
| | | |||||
| * | Remove `#among?` from Active Support | Prem Sichanugrist | 2011-04-13 | 1 | -1/+1 |
| | | | | | | | After a long list of discussion about the performance problem from using varargs and the reason that we can't find a great pair for it, it would be best to remove support for it for now. It will come back if we can find a good pair for it. For now, Bon Voyage, `#among?`. | ||||
| * | Change Object#either? to Object#among? -- thanks to @jamesarosen for the ↵ | David Heinemeier Hansson | 2011-04-12 | 1 | -1/+1 |
| | | | | | suggestion! | ||||
| * | Using Object#in? and Object#either? in various places | Prem Sichanugrist | 2011-04-11 | 1 | -1/+2 |
| | | | | | There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?. | ||||
| * | Delete blank lines in migration generator | Santiago Pastorino | 2011-02-02 | 1 | -3/+2 |
| | | |||||
| * | Configurable generation of add_index for references columns | Michał Łomnicki | 2011-02-01 | 2 | -0/+3 |
| | | | | | Signed-off-by: Santiago Pastorino <santiago@wyeworks.com> | ||||
| * | Use Rails 3.1 `change` method in 'add_' migration generator | Prem Sichanugrist | 2011-01-04 | 1 | -0/+8 |
| | | |||||
| * | Use Rails 3.1 `change` method in model generator | Prem Sichanugrist | 2011-01-04 | 1 | -5/+1 |
| | | |||||
| * | Generate add_index by default when giving type belongs_to or references | Santiago Pastorino | 2010-12-16 | 1 | -0/+4 |
| | | |||||
| * | updating generators | Aaron Patterson | 2010-11-17 | 3 | -6/+6 |
| | | |||||
| * | Add namespacing for observer generator | Piotr Sarnacki | 2010-09-25 | 1 | -0/+2 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Generators fix: properly check if module should be created when creating a ↵ | Piotr Sarnacki | 2010-09-25 | 1 | -1/+1 |
| | | | | | | | namespaced model Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Refactor namespaced generators to use module_namespacing block helper | Piotr Sarnacki | 2010-09-24 | 3 | -2/+6 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Generators are not aware of namespace of isolated engines and applications | Piotr Sarnacki | 2010-09-24 | 1 | -2/+2 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Implemented ActiveRecord::Migrations#copy based on James Adam's idea | Piotr Sarnacki | 2010-09-03 | 1 | -0/+6 |
| | | | | | | | | | | | | | | | | ActiveRecord::Migration#copy allows to copy migrations from one place to another, changing migrations versions and adding scope to filename. For example: ActiveRecord::Migration.copy("db/migrate", :blog_engine => "vendor/gems/blog/db/migrate") will copy all migrations from vendor/gems/blog/db/migrate to db/migrate with such format: Versions of copied migrations will be reversioned to be appended after migrations that already exists in db/migrate | ||||
| * | split out active_record migration logic so others can easily reuse [#5389 ↵ | Jack Dempsey | 2010-09-01 | 2 | -10/+17 |
| | | | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Avoid a blank line before the add/remove columns | Santiago Pastorino | 2010-06-25 | 1 | -2/+2 |
| | | |||||
| * | Line break in migration template and nicer code indentation | Łukasz Strzałkowski | 2010-06-25 | 1 | -6/+8 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Patch for Namespace problem in Scaffold. [#4763 state:resolved] | Mohammed Siddick.E | 2010-06-23 | 1 | -1/+1 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Fix problem with migrations template that can cause bogus code to be created | Steve Abatangle | 2010-06-20 | 1 | -4/+8 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Update generators to use thor 0.13.6 with simpler source_root handling. | José Valim | 2010-04-30 | 1 | -7/+3 |
| | | |||||
| * | Make the migration generator handle pre-existing migrations with the same ↵ | Phil Smith | 2010-04-19 | 1 | -2/+3 |
| | | | | | | | | | | | timestamp. In the event a migration already exists with that number, the new migration's timestamp will be incremented by 1. [#4412 state:resolved] Signed-off-by: Michael Koziarski <michael@koziarski.com> | ||||
| * | Generate module file for namespaced models [#4230 state:resolved] | Andrew White | 2010-04-12 | 2 | -0/+10 |
| | | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
| * | Load generators from both lib/rails/generators and lib/generators. Using the ↵ | José Valim | 2010-03-23 | 10 | -0/+177 |
| former since it's less obstrusive. | |||||
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |