This article is part two of the series about Rails Migrations and it will explain on a deeper level how to use the Ruby on Rails migrations.

After we spoke about Migrations in our previous article found here we understood the basics needed to use Migrations in Ruby on Rails.

Now to begin with the code and something we did not mention earlier.

You see indexes are something that a good database design MUST contain!
This example shows how to add and remove an indexed field.

And now let’s take a look at some examples which might or might not be so obvious to make.

Read the rest of this entry »

Recently I was asked the following question:

“How hard is it to build this project in Rails”

You can substitute this with anything. After a short period of time I realized that such a question can’t be really answered to a point where a programmer would agree completely if he/she didn’t even touched Ruby on Rails. In order to change that fact a person should see the whole process of developing and deploying a Rails application so he/she can realize the power and potential of a Rails application.

With all this in mind I hereby announce the Project type articles of RubyCorner.net. Those articles will represent an overview of the development process of a real working Rails web application. This article is the first of the series Project and it will begin not so briefly and give a more detailed overview of the things we will do. The next articles in the series will focus on more complex things and will skip those explained before assuming the knowledge was already obtained.

Let’s begin with our first web application project:

Project 1 – Developing a News site in Rails
parts count: 3 (this is a three day project)

Rails version used: 1.2.3 (used both on Windows and Linux platform)
Ruby version used: 1.8.5 (used both on Windows and Linux platform)
Knowledge of HTML and CSS: assumed
Knowledge of a Web Programming Language and Database: Basic-Advanced assumed

Read the rest of this entry »

I found an interesting topic recently in a forum discussion. It was about whether or not an eBay clone could be build on the top of Ruby on Rails. A few interesting questions are: “Is RoR the best toolkit for doing that?”, “Whether the
same eBay functionality could be accomplished?” or “Could it scale enough?”
Read the rest of this entry »

  Programming languages and tools from the business point of view  

Programming languages and tools are considered only for developers but smart companies have understood that in order to achieve best results they should not only care for business but for developers too. And what kind of better care than the one for programmers happiness and productivity by suppling them with the best tools available? This article intention is to point out in a bit of a story like form how Rails helps. It will go from the ways of developing a web application and points out some of the aspect in business and development which are really useful when a company chooses to use Rails for it’s development tool.

Read the rest of this entry »

Not more than two months ago I started programming in Ruby. Ofcourse using the rails framework. It was superb for me to find that just everything about web development is already there in the framework. The directory structure - it’s just so easy and you intuitively find whatever you need, logging - it has that useful feature to tell you the performance of your business logic as well as the performance of rendering the view. Ruby on Rails clearly MVC based. Working with and refactoring of your DB is an ease with the help of migrations. You’ve heard about Web 2.0 - yes, AJAX is well incorporated into the rails, too. I still haven’t found a missing part.

Why a Developer but not a Coder? Well, you should feel the beauty to develop in Rails. For me a CODER is someone who concentrates on code structure and thinks about how to CODE down the business logic for his problem. The Coder is also highly considering the difficulties for accessing his DB. What’s the contrast in case of using Ruby on Rails. Just after a little experience, you don’t code down - you write down whatever you need. Moreover you are not scared to think about adding new functionality related to DB Objects - you just tell rails that you want it. All this ease lets you think on a higher level and lets you concentrate on the real problems that should be solved.

Read the rest of this entry »