search

SEI-ATL / UNIT_2

This repo is for all things Unit 2
0 stars 3 forks source link

Pete's Pod #20

Closed romebell closed 3 years ago

romebell commented 3 years ago

Add your link to the ISSUE that you create here. Be sure to assign your Pod Leader

anonyymous1 commented 3 years ago

Looked into searching with an array, thats a no go. Also, did research on the restrictions of what you can store to your DB and it seems like the creator doesn't mind what you do with it. My next questions is does it makes sense to store everything for a persons favorite so that it doesn't request from the API a lot like we discussed OR should I store the main attributes like I did below?

I also have a question about how my join table should look:

Screen Shot 2020-11-30 at 11 30 19 AM

Screen Shot 2020-11-30 at 11 49 57 AM

pmacaluso3 commented 3 years ago

Re: what to store, I'd say store everything you think you could want to display, erring on the side of grabbing too much. Re: how the favorites table should look, you definitely want it (and all tables) to have a PK id field