Finishing Database on models.py

[neXgithub]

Time: 1 hour Task: Redesign detabase Deliverable: List of tables with primary and secondary keys Person: Nick

Completed:

• ERD diagram in lucid chart and the technical doc
• Tables along the primary keys and foreign keys in the technical doc -> Code Structure -> Database

[neXgithub]

Andrew said a. Checking that bosses won't be able to wishlist their own jobs. I was taught to do it in views.py later by just writing if job.boss is not user: add it to wishlist

[andrewsiah]

Andrew to update django models.py according to Nicholas' specification. On it righto

[andrewsiah]

@neXgithub Per your database design, questions:

On User, why:

1. Date
2. GeoLocation & Address both needed?

Why both Tags and Categorisation??

[neXgithub]

Date = when they subscribed/ signed up.

• useful for validation and for stats, and to make some searching faster Geolocation = either latitude/ longitude or google maps location data Address = street, house number ect
• cause unless we want to query google maps, or use Geodjango every time we a. want to display an address b. want to search based on city c. want to search based on zip code we would want a representation of the actual address too

2. Categorization is a linking table https://en.wikipedia.org/wiki/Associative_entity Its so that we do not have a many to many relationship. That really messed up the database

3. next time we do a database design Ill add the data type.

4. Things like address/ name should be broken down into subfields like first name, last name, street number, city, country, zip-code

[andrewsiah]

@neXgithub

On 2 (Categorization & Tagging),

Isn't it always a one-to-many relationship tho?

EG Job 1 - Title: Pull weed from my garden. Tag: Gardening

EG Job 2 - Title: Clean my garden Tag: Gardening

IE: Many jobs to one tag. No jobs have more than one tag.

Or you have a more specific categorization (kinda like labels) in mind? But that's too much complexity and harms our minimalistic end-goals no? Or am I missing something here?

[neXgithub]

did you push your changes for the model? Cause I do not see any changes on the model file and I've pulled

[neXgithub]

Ignore the shifts back and forth, mistyped.