Skip to main content

Experiences Using "Build Your Own Ruby On Rails Web Applications"

This is the first of a series of tech posts on this blog. I'm studying RubyOnRails, (RoR), using an excellent book: Build Your Own Ruby On Rails Web Applications . The book is easy to understand and flows well in a narrative fashion with plenty of humor thrown in. As I build my real-world application I'll post notes of interest here. These posts are intended for RubyOnRails beginners or others reading the book.

Model class to database table naming:
I understood from the book that a model class like 'Story' would be translated into a table name in a migration file of 'story'. What I was not aware of was that a name like 'MyBigStory' will be translated into a table name of 'my_big_story'.

rake and rolling back database migrations:
First, this feature of RoR is incredible! Essentially it's revision control for database schemas! With a minimum of work, the developer can maintain a framework that allows her to easily move back and forth between versions of the schema. The generated migration files go a long ways towards making this feature convenient to use.

There is a typo in the book around rolling back versions. The command in the book is:

rake db:migrate -VERSION=n

the command should read:

rake db:migrate VERSION=n

Most importantly, this typo led me to re-read the beginning of the book where it is noted that all errata will be published at the books online errata page.

Of course, the question arises, why did I need to do a rollback of a schema so soon? I typed in an incorrect column name for a table column. So, on page 187 of the book where the author adds a story_id column, I added a stary_id column. Because of the errata, I was unable to roll back the migration. It didn't seem right to roll back the migration and lose the development history anyway. So, I moved forward and created a new migration to correct the misnaming.

First, ruby was used to create a new migration file:

rruby script/generate migration RenameID

The new migration simply used the following rename_column method in the migration file's self.up method:

rename_column :votes, :stary_id, :story_id

In the self.down method, the change was reversed with:


rename_column :votes, :story_id, :stary_id

I then ran

rake db:migrate

rake pulled in the new migration file, changed the column name and all was well!


Comments

Popular posts from this blog

More Cowbell! Record Production using Google Forms and Charts

First, the what : This article shows how to embed a new Google Form into any web page. To demonstrate ths, a chart and form that allow blog readers to control the recording levels of each instrument in Blue Oyster Cult's "(Don't Fear) The Reaper" is used. HTML code from the Google version of the form included on this page is shown and the parts that need to be modified are highlighted. Next, the why : Google recently released an e-mail form feature that allows users of Google Documents to create an e-mail a form that automatically places each user's input into an associated spreadsheet. As it turns out, with a little bit of work, the forms that are created by Google Docs can be embedded into any web page. Now, The Goods: Click on the instrument you want turned up, click the submit button and then refresh the page. Through the magic of Google Forms as soon as you click on submit and refresh this web page, the data chart will update immediately. Turn up the:

Cool Math Tricks: Deriving the Divergence, (Del or Nabla) into New (Cylindrical) Coordinate Systems

Now available as a Kindle ebook for 99 cents ! Get a spiffy ebook, and fund more physics The following is a pretty lengthy procedure, but converting the divergence, (nabla, del) operator between coordinate systems comes up pretty often. While there are tables for converting between common coordinate systems , there seem to be fewer explanations of the procedure for deriving the conversion, so here goes! What do we actually want? To convert the Cartesian nabla to the nabla for another coordinate system, say… cylindrical coordinates. What we’ll need: 1. The Cartesian Nabla: 2. A set of equations relating the Cartesian coordinates to cylindrical coordinates: 3. A set of equations relating the Cartesian basis vectors to the basis vectors of the new coordinate system: How to do it: Use the chain rule for differentiation to convert the derivatives with respect to the Cartesian variables to derivatives with respect to the cylindrical variables. The chain

The Valentine's Day Magnetic Monopole

There's an assymetry to the form of the two Maxwell's equations shown in picture 1.  While the divergence of the electric field is proportional to the electric charge density at a given point, the divergence of the magnetic field is equal to zero.  This is typically explained in the following way.  While we know that electrons, the fundamental electric charge carriers exist, evidence seems to indicate that magnetic monopoles, the particles that would carry magnetic 'charge', either don't exist, or, the energies required to create them are so high that they are exceedingly rare.  That doesn't stop us from looking for them though! Keeping with the theme of Fairbank[1] and his academic progeny over the semester break, today's post is about the discovery of a magnetic monopole candidate event by one of the Fairbank's graduate students, Blas Cabrera[2].  Cabrera was utilizing a loop type of magnetic monopole detector.  Its operation is in concept very sim