Db

The point of Schema Initially I was surprised that the code below logs anything out at all. const uri = process.env.DB_URL; const port = process.env.PORT || 3000; const localTest = "mongodb://127.0.0.1:27017/test" const express = require("express") const mongoose = require("mongoose") const app = express() app.use(express.static("public")) main().catch((err) => console.log(err)) async function main() { await mongoose.connect(localTest) } // There is no "goingCrazy" property in Kitten // There is instead a "name" property of the type String....

So the point of Schema is to define what properties can be read. The point of model is instead to define what collection is read. Try const uri = process.env.DB_URL; const port = process.env.PORT || 3000; const localTest = "mongodb://127.0.0.1:27017/test" const express = require("express") const mongoose = require("mongoose") const app = express() app.use(express.static("public")) main().catch((err) => console.log(err)) async function main() { await mongoose.connect(localTest) } // There is no "goingCrazy" property in Kitten // There is instead a "name" property of the type String....