database information

[97revenge]

A conceptual database relationship.

catalog_name would be like the name of each area of ​​a menu , a macro-item such as sweet bread would be in bakery .

CREATE TABLE "catalog" (
  "catalog_name" varchar PRIMARY KEY DEFAULT 'palavra chave de criterios',
  "catalog_init" varchar DEFAULT 'primeiro item do cardápio',
  "catalog_mid" varchar DEFAULT 'segundo item do cardápio',
  "catalog_low" varchar DEFAULT 'terceiro item do cardápio'
);

What should be done

• mongoDB and mongoose setup in gree-menu.
• manage primary keys and analyze better ways to stream data with Object-relational mapping
• database integration and POST and GET requests.

dbdiagram.io

[97revenge]

what we really did

• mongoDB and mongoose setup in gree-menu. 👍
• we managed to test a non-conceptual data model and realized that it is the ideal model for the project
• database integration and POST and GET requests. 👎

const mongoose = require('mongoose');
const { Schema, model } = require('mongoose');
const { v4: uuidv4 } = require('uuid');

const catalogDB = new Schema({
  catalogName: String,
  catalogInit: String,
  catalogMid: String,
  catalogLow: String,
  id: String // uuid instance
})
const catalog = model('catalog', catalogDB)

the model and the Schema of catalog

Path generator functions and dependency insight .

I'm usually thinking about creating coupled functions but working together, like a car factory.

const generatePath = (req, res) => {
  const directedUrl = (`/`).concat(req)
  return directedUrl
}

generatePath creates path strings for .get() and .post() functions

The most common way to think of the development and production layer

"scripts": { "dev": "nodemon app.js", "main": "node app.js" },