The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
Rails lesson learned

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Daniel Berger

Posts: 1383
Nickname: djberg96
Registered: Sep, 2004

Daniel Berger is a Ruby Programmer who also dabbles in C and Perl
Rails lesson learned Posted: Mar 15, 2007 11:42 AM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Daniel Berger.
Original Post: Rails lesson learned
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Daniel Berger
Latest Posts From Testing 1,2,3...

Advertisement
Today I learned a hard lesson with regards to migrations: always do your fixture loading *last*. Why? If you alter the table's schema, presumably you'll want to update your fixture data. But, if you try loading the new fixture data before you've altered the schema, it's going to choke.

From now on I've decided that all load migrations will start with "100_".

In other news I was sad to see that the postgres adapter (even with the changes made by Bertram Scharpf) doesn't return array datatypes as an array. Instead, you get what looks like a stringified hash. I guess that's what read_attribute is for. :)

Read: Rails lesson learned

Topic: ActiveScaffold for Rails - RC1 Released Previous Topic   Next Topic Topic: Function Pointers in RubyCocoa

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use