Rails%203%20In%20Action

218 CHAPTER 9 File uploading
remove_column :tickets, :asset_file_size
remove_column :tickets, :asset_updated_at
end
end
Remember that you call the field asset internally, but to the user, it’s called File? This
column-naming convention is the reason for the different names. To ease confusion
for people working on the application (you!), you call these fields with the asset prefix
so that the column names are asset_file_name and not file_file_name. There’s
also another reason, which is explained in section 9.2.
To add these columns to your development environment’s database, run rake db
:migrate. Then run rake db:test:prepare to add them to your test environment’s
database. If you run the feature with bin/cucumber features/creating_tickets
.feature, all the scenarios that were previously passing are still passing. But the scenario
you just added fails with this error:
Then I should see "speed.txt" within "#ticket .asset"
You can see that the scenario failed because Capybara can’t find the text within this
element on the TicketsController’s show page: this text and this element don’t
exist! You need to add at least the filename for your scenario to pass, so add it underneath
the spot in the show view where you currently have the following:
Created by
You must also wrap all the code in this view inside a div tag with the id attribute
ticket and spice it up a little by adding the content type and file size there too, as
shown in the following listing.
Listing 9.5 app/views/tickets/show.html.erb
Created by
Attached File
()
Provide
download link
Here you use the exists? method defined on the asset method (which was defined
by Paperclip and returns a Paperclip::Attachment object); the exists? method
returns true if the file exists. You use it because you don’t want it trying to display the
path or any other information of a file when there isn’t one.
B