Rails%203%20In%20Action

20 CHAPTER 1 Ruby on Rails, the framework
As you can see by this example, the validations you defined in your Purchase model
take effect for both the creation and updating of records automatically.
Now what would happen if, rather than update a purchase, you wanted to delete
it? That’s built in to the scaffold too.
1.2.11 Deleting
In Rails, delete is given a much more forceful name: destroy. This is another sensible
name because to destroy a record is to put an end to its existence. 16 Once this record’s
gone, it’s gone, baby, gone.
You can destroy a record by going to http://localhost:3000/purchases and clicking
the Destroy link shown in figure 1.11 and then clicking OK on the confirmation
box that pops up.
When that record’s destroyed, you’re taken back to the Listing Purchases page.
You’ll see that the record no longer exists. You should now only have one record, as
shown in figure 1.12.
How does all of this work? Let’s look at the index template in the following listing
to understand, specifically the part that’s used to list the purchases.
'Are you sure?',
:method => :delete %>
16 Mac OS X dictionary.
Listing 1.16 app/views/purchases/index.html.erb
Figure 1.11 Destroy! Figure 1.12 Last record standing