CRUD in Sinatra -- Check for Understanding

cfu_crud_in_sinatra.markdown

1. Define CRUD.

   • Create, Read, Update, Delete. Describes the type of actions one should be able to do to the database.

2. There are seven verb + path combinations that are necessary in a basic Sinatra app in order to provide full CRUD functionality. List each of the seven combinations, and explain what each is for.

   • 1. See all: '/tasks' + GET
   • 2. See one: '/tasks/:id' + GET
   • 3. Form to create (part 1): '/tasks/new' + GET
   • 4. Create from form (part 2): '/tasks' + POST
   • 5. Form to update (part 1): '/tasks/:id/edit' + GET
   • 6. Update from form (part 2): '/tasks/:id' + PUT
   • 7. Delete one: '/tasks/:id' + DELETE

3. Why do we use set method_override: true?

   • Modern browsers have not agreed upon a way to use PUT or DELETE yet. As a result, we have to use a few creative solutions to be able to use these other 2 verbs, and they use method_override to do it.

4. Explain the difference between value and name in this line: <input type='text' name='task[title]' value="<%= @task.title %>"/>.

   • I believe that in this instance the 'name' is being used to denote by what name the data being input will be referred to, while the 'value' is what that data actually is.

5. What are params? Where do they come from?

   • Params are the data input by the user, they come from the form fields provided in the app.

Looks good!
#4: value is what will be displayed in the html to the user
#5: params can also come from the URL