search for: tiralorn

Hi. What is the best way to pre-populate your database with records while developing, not testing? For example, I want to: 1) > [run this command to populate db] 2) > ruby script/server 3) now I can surf to localhost:3000 and my app will already have relevant data I''m hoping to use yaml to suck it in. Is there a way to use the Fixture class to handle this even though this is

I want to print my timestamp objects in a specific format. I want to print a date like this: Sunday, January 8 2006 I don''t want it to print January 08. For the time, I want it to look like this: 9:08 pm Not 09:08 and lower case PM. I created these methods: def format_date(date) date.strftime("%A, %B #{date.day} #{date.year}") end def format_time(date) if

I''ve been playing around with EdgeRails and checking out some of the new features. The one that will probably have the biggest affect on my designs is join models (or :through associations). For those not familiar with this feature, it lets you replace your habtm association with a pair of has_many associations indirected through an intermediate model class. Looks like good

According to the Hivelogic instructions <http://hivelogic.com/ articles/2005/12/01/ruby_rails_lighttpd_mysql_tiger> to correctly installing RoR on Tiger: > With RubyGems installed, Rails is a simple, one-line install: > > sudo gem install rails --include-dependencies > > Some people following these instructions report one of two errors > after performing this step.

Are my eyes going buggy, or did something recently change in Edge Rails so that now scaffolds are generated with pluralized controller/ helper/etc names? I peeked at the code in railties/lib/rails_generator/generators/components/scaffold/ scaffold_generator.rb around line 50, and it looks like there was a change there recently so that it now defaults to pluralized names. So why was this

I''m getting tired of creating working data in my db just so that I can mess it up while working on the code. I''ve been using Ruby code to create initial working data, however my data model is getting complex enough that it''s becoming a pain to maintain this code. I''ve been thinking about using YAML fixtures for this purpose, but there''s no obvious

I haven''t seen a note here on the list, so in case anyone doesn''t have their RSS reader glued to the relevant blogs... http://weblog.rubyonrails.org/articles/2006/03/28/rails-1-1-rjs- active-record-respond_to-integration-tests-and-500-other-things Congrats to David and all the core team, and thanks for your dedication and all the work. This release looks really solid and

I started with Ruby on Rails in the 0.13.x period, so I''m sure I missed out on a lot of history. There''s probably some good explanation for something I''ve been wondering about, but I haven''t seen it written down anywhere. Maybe someone can clue me in. I''ve always felt that one of the uglier APIs was the ActiveRecord::find() method. I call