Schema:

[PLUCS2]

• Users:
• [x] location - good bonus feature, should be a foreign key to a location table
• Location
• [x] there is a ruby gem and a way with google maps search bar api to convert string addresses to latitude and longitude (which is needed for google maps api)
• [x] Location table has name as string (ie New York, Los Angeles, etc.)
• Cafes:
• [x] Combine street, city, country to address which is a string
• [x] add a latitude and longitude column that expects a float data type
• [x] average rating must be a float if it wants to have decimals and not be a whole number

[KoKo-debug]

I'm confused on how user location works. Are we talking about getting their location based on the ip address? if not, it seems like we are getting their location based on the address that they submit on user sign up/profile page. is that correct?

I was originally thinking about just having a user select their general location from a drop-down list of cities/countries

[KoKo-debug]

Oh! were you talking about this feature on opentable?

It looks like you're in Manhattan. Not correct? Get current location

and when u click "Get current location" it finds where I am after I allow my location to be shared? (also it seems like it knows my location anyways because it says "looks like you're in Manhattan")

[KoKo-debug]

I left address and name without null:false. Is that correct?

users don't need address, just location name linked to a long and lat while restaurants need address to get long and lat and won't have a need for name.

is what I was thinking.