search for: some_oth

...e DB, modify the table''s structure, then go and modify EVERY insert statement. The insert statements look like (from memory): INSERT INTO my_table VALUES (''some_id'', ''some_val'', '''', '''', '''', ''some_other val'', '''', '''', '''', '''') Assuming a my_table def like: CREATE TABLE my_table ( id, something, something_else, another_something, etc etc); So, modifying those INSERT statements suck. vim helps a little bit...

If (like me) you use ccrb to test a Rails app and (like me) you define your own :cruise task, because, for example, you use rspec rather than Test::Unit and (like me) you have the RAILS_ENV ||= ''production'' line in environment.rb (because, like me, you use crummy shared hosting) Your build will run in production mode, possibly screwing up your production database,

When I first learned about the View specs I was very excited. I still am. However, I haven''t found them useful yet for one reason. They throw the following exception when ever a view renders another view, which is very common. ActionView::TemplateError in ''Event View message'' No rhtml, rxml, rjs or delegate template found for spec/rails/ view_spec/_info

I''m trying to use rspec to test a controller that has ajax. I have the following action: def change_ad_type_form render :update do |page| page.replace_html ''ad_sub_form'', :partial => ''text'' end end and the following spec: specify "should return Text subform on AJAX request to change_ad_type_form" do