On 03/12/2010 04:03 PM, Mohammed Morsi wrote:
> On 03/11/2010 05:28 PM, Jason Guiditta wrote:
>
>> ---
>> src/db/migrate/20090917192602_create_users.rb | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/src/db/migrate/20090917192602_create_users.rb
>> b/src/db/migrate/20090917192602_create_users.rb
>> index 5b9f76e..67706fb 100644
>> --- a/src/db/migrate/20090917192602_create_users.rb
>> +++ b/src/db/migrate/20090917192602_create_users.rb
>> @@ -29,6 +29,8 @@ class CreateUsers< ActiveRecord::Migration
>> t.string :persistence_token, :null => false
>> t.string :single_access_token, :null => false
>> t.string :perishable_token, :null => false
>> + t.string :first_name
>> + t.string :last_name
>> # Magic columns, just like ActiveRecord's created_at and updated_at.
>> # These are automatically maintained by Authlogic if they are
>> present.
>> t.integer :login_count, :null => false, :default => 0
>>
>>
> NACK. Can you create a seperate new migration that alters the user table
> (adding the column on up, dropping it on remove).
>
> Committed migrations shouldn't be edited, I had to blow away / recreate
> my db to get first_name / last_name.
>
> -Mo
> _______________________________________________
> deltacloud-devel mailing list
> [email protected]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
ACK. Since it doesn't seem that at this early point in the dev process,
migrations consistency is high priority and it would just lead to clutter.
-Mo
_______________________________________________
deltacloud-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/deltacloud-devel
