Use findAll() with include() and sequelize.fn() for the COUNT: Location.findAll({ attributes: { include: [[Sequelize.fn(“COUNT”, Sequelize.col(“sensors.id”)), “sensorCount”]] }, include: [{ model: Sensor, attributes: [] }] }); Or, you may need to add a group as well: Location.findAll({ attributes: { include: [[Sequelize.fn(“COUNT”, Sequelize.col(“sensors.id”)), “sensorCount”]] }, include: [{ model: Sensor, attributes: [] }], group: [‘Location.id’] })
According to the doc : If you do not provide other arguments than the SQL, raw will be assumed to the true, and sequelize will not try to do any formatting to the results of the query. That being said : The Sequelize object has a [options.query={}] optional parameter to set default options for sequelize.query. … Read more
Your best option is: return Customer.findAll({ attributes: Object.keys(Customer.attributes).concat([ [sequelize.literal(‘(SELECT SUM(“Orders”.”amount”) FROM “Orders” WHERE “Orders”.”CustomerId” = “Customer”.”id”)’), ‘totalAmount’] ]) }); This looks like an extension to issue #1869: Querying on the through model/join table is not possible currently unfortuneatly. Your question is also tangentially related to this one, where the question there was sort of a … Read more
While the accepted answer isn’t technically wrong, it doesn’t answer the original question nor the follow up question in the comments, which was what I came here looking for. But I figured it out, so here goes. If you want to find all Posts that have Users (and only the ones that have users) where … Read more
Insteaf of localhost point to mysql which is the service name (DNS) that nodejs will resolve into the MySQL container: DB_HOSTNAME: mysql And { … host: ‘mysql’, … }
If you don’t want to recreate your model from scratch, you can manually generate a migration file using the following CLI command: sequelize migration:generate –name [name_of_your_migration] This will generate a blank skeleton migration file. While it doesn’t copy your model structure over to the file, I do find it easier and cleaner than regenerating everything. … Read more
Sequelize Association Cheatsheet Updated for Sequelize v2/3/4/5 Generally I think the problems are that we are confused about what tables created, and what methods are gained by associations. Note: Defining foreignKey or cross table name are optional. Sequelize automatically creates it, but defining it allows coders to read the models and find out what the … Read more
You can pass a logging option when initializing sequelize, which can either be a function or console.log var sequelize = new Sequelize(‘database’, ‘username’, ‘password’, { logging: console.log logging: function (str) { // do your own logging } }); You can also pass a logging option to .sync if you only want to view the table … Read more
Your DATABASE_URL refers to 127.0.0.1, which is the loopback adapter (more here). This means “connect to myself”. When running both applications (without using Docker) on the same host, they are both addressable on the same adapter (also known as localhost). When running both applications in containers they are not both on localhost as before. Instead … Read more
All models should be registered in one place as long as their associations: database.js const fs = require(‘fs’) const path = require(‘path’) const Sequelize = require(‘sequelize’) const db = {} const models = path.join(__dirname, ‘models’) // correct it to path where your model files are const sequelize = new Sequelize(/* your connection settings here */) … Read more