Hi Chris, Yeah, that was a bug in the migration. I've removed it in the Rails3 branch. Please try installing again and let me know if you run into trouble.
Thanks, Bruno On Thu, Apr 21, 2011 at 3:38 PM, Chris Schumann <[email protected]>wrote: > I created a method to return the login as the login_slug. What kind of hurt > have I signed up for with that? > > It seems that the migrations have a ton of assumptions about what models > are available and what is in them before they begin. Here's a collection so > far: > > - No Tags or Taggins table exist > - users does not have a zip code > - tags and taggings don't have indexes > - users has an avatar_id column > - users has a vendor column > - users don't already have a role system > - users has a boolean admin column > - users has a crypted_password column > - users has a salt column > - users has a remember_token column > - users has a remember_token_expires_at column > - something about AuthLogic > - users has a login column, unindexed > - users has a persistence token column, unindexed > - users has a last_request_at column, unindexed > > Doesn't seem very friendly to existing apps. Perhaps it would be better to > make a new table, and have that belong_to user, with a corresponding > user_id. It would be much easier to add a "has_one :something" to my user > model than to edit the migrations. > > > Thanks, > Chris > > -- > You received this message because you are subscribed to the Google Groups > "CommunityEngine" 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/communityengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "CommunityEngine" 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/communityengine?hl=en.
