The "integer", "string" and "float" methods are just shorthands for the column call using that type.
It's also the "new way" (new since Rails 2, not that new now) of writing migrations. And the "timestamps" will create both a created_at and also an updated_at column. - Maurício Linhares http://alinhavado.wordpress.com/ (pt-br) | http://codeshooter.wordpress.com/ (en) On Fri, Jun 5, 2009 at 11:10 PM, J. D.<[email protected]> wrote: > > The first scaffold table should look like this: (not what I posted) > > class CreateRushingOffenses < ActiveRecord::Migration > def self.up > create_table :rushing_offenses do |t| > t.string :name > t.integer :games > t.integer :carries > t.integer :net > t.float :avg > t.integer :tds > t.float :ydspg > t.integer :wins > t.integer :losses > t.integer :ties > > t.timestamps > end > end > > def self.down > drop_table :rushing_offenses > end > end > > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
