Austin
Dave/Steven
A Viking eCommerce store for Thunder Gods that like to buy "Antique Wooden Pizzas"
#Overview
SQL Products/Searching
NoSQL for the Analytics
#In Depth Org of Data SQL
- usr table
- id
- username
- shipping address table
- id
- usrid as foreign key
- address
- city
- state
- categories
- id
- category name
- products
- id
- sku
- categoryid as foreing key
- name
- price
- description
- jpg url to public folder
no table for cart or session AKA rework this later - cookie in browser will store product ids - actually we'll implement ^^ with sessions - a user session can be stored in two main ways with cookies: on the server or on the client. This module stores the session data on the client within a cookie, while a module like express-session stores only a session identifier on the client within a cookie and stores the session data on the server, typically in a database.
- notes that rework
- session multi def.
- a place server (not database) in-memory where you store some info and id that place
with the cookie
- express-session will id specific sessions for each user
- secret to resolve every cookie
- add an object to req.session (that object will have all product ids)
- akakaka just use cookie-session for now and skip express-session
notes - when user presses buy remove cookie and create row in orders table + take order id and create rows in OP
NoSQL
- orders collection
- keys
- id
- shippingaddressid from SQL
- userid from SQL
- productsId array
- keys
stripe will send info and we take that info and put it in mongodb