# Database Schema:

[Evan-Leon]

• [x] Contains correct datatypes
• [x] Contains appropriate constraints/details
  • [x] primary key
  • [x] not null
  • [x] unique
  • [x] indexed
  • [x] foreign key
• [x] Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
• [x] foreign key and table name are lowercased, snake_cased and back_ticked
• [x] Correctly formatted
  • [x] schema is written in a table format
  • [x] the table’s name are lowercased, snake_cased and back_ticked
  • [x] the table header column names are bolded
  • [x] columns names are lowercased and snaked_cased and back_ticked

[Evan-Leon]

• Look to cohort wiki for formatting guidance
• location will likely need lat and lng (look to benchbnb for guidance)
• might want index on location name (for easier searching) Other than that great work on the joins tables! 🔥

[elliot-wilson]

I've added the lat/lng fields to location and started indexing on location title.

One thing I'll be looking up over the weekend: Is it possible to use the Google Maps API to autofill the lat/lng based on the address? Ideally users won't actually have to look up the coordinates of a location; the app will take its best guess (and allow people to override if they want).

[Evan-Leon]

Schema looks good now!

Not sure about your question in regards to google maps api, i'm guessing that must be a type of functionality, I will try to take a look at that, also let me know what you find!