sequelize.js

I have the following model hierarchy: User.hasMany(Child); Child.hasMany(Profile); Once I have a User object loaded, I need to load its Children and their associated Profiles according to the following logic: Load all Children for the User , sorted by name . For each Child , load the first three Profiles reverse sorted by id . Is there a way to limit and sort the eager-loaded Profiles ? I can limit and sort the Children but not the Profiles . user.getChildren({ limit: 10, order: [['name', 'ASC']], include: [{ model: Profile, limit: 3, <-- HAS NO EFFECT!!! order: [['id', 'DESC']] <-- HAS NO

I am using the sequelize ORM in my nodejs app and it seems that it drops table in the wrong order when I sequelize.sync({force: true}) For example, with: var StationEntity = sequelize.define('Station', { id: { type: Sequelize.INTEGER, primaryKey: true, allowNull: false}, name: { type: Sequelize.STRING, allowNull: false} }) var StationSnapshotEntity = sequelize.define('StationSnapshot', { id: { type: Sequelize.BIGINT, autoIncrement: true, primaryKey: true}, snapshotTimestamp: { type: Sequelize.BIGINT, allowNull: false} }) StationEntity.hasMany(StationSnapshotEntity, {as: 'Snapshots',

Is there a way that I could use a base class that has all the common attributes and methods for my models but not linked with a database table, and then I could extend this base class when defining new models. Here I have created the base, person model in node express. I need the person class to be extended from the base class. const person = sequelizeClient.define('person', { name: { type: DataTypes.STRING, allowNull: false } }, { hooks: { beforeCount(options) { options.raw = true; } } }); const base = sequelizeClient.define('base', { id: { type: Sequelize.INTEGER, autoIncrement: true,

I'm adding a unique constraint in a migration via the migrations.changeColumn function. Adding the constraint works, but since you need to provide a “backwards migration“, removing it the same way does not. It doesn't give any errors when migrating backwards, but again applying the forward migration results in Possibly unhandled SequelizeDatabaseError: relation "myAttribute_unique_idx" already exists . (The used database is postgres) module.exports = { up: function (migration, DataTypes, done) { migration.changeColumn( 'Users', 'myAttribute', { type: DataTypes.STRING, unique: true // ADDING

I am using sequelize ORM in node js. I am join two table and get result but that result return with table name as prefix. var Sequelize = require('sequelize'); var sequelize = new Sequelize('test', 'root', '', { // configuration } }); const db = {}; db.Sequelize = Sequelize; db.sequelize = sequelize; db.role = require('./../model/definitions/role')(sequelize, Sequelize); db.admin = require('./../model/definitions/admin')(sequelize, Sequelize); db.admin.findAll({ include: [{ model: db.role, where:{status : 'Active'}, }], raw: true }).then(function(result) { console.log(result); }).catch

I'm trying to run 2 promises in paralel with sequelize, and then render the results in a .ejs template, but I'm receiving this error: Promise.all(...).spread is not a function This is my code: var environment_hash = req.session.passport.user.environment_hash; var Template = require('../models/index').Template; var List = require('../models/index').List; var values = { where: { environment_hash: environment_hash, is_deleted: 0 } }; template = Template.findAll(values); list = List.findAll(values); Promise.all([template,list]).spread(function(templates,lists) { res.render('campaign/create.ejs', {

I've been performing kind of intensive schema dropping and creating over a PostgreSQL server, ERROR: out of shared memory HINT: You might need to increase max_locks_per_transaction. I need to increase max_locks_per_transaction but how can i increase it in MAC OSX you might find ../data/postgresql.conf file, then edit with notepad, set max_locks_per_transaction = 1024 if it looks like # max_locks_per_transaction... you must remove #. it must look like that: max_locks_per_transaction = 1024 # min 10 than save it and restart postgresql It is a setting in your postgresql.conf if you do not know

I am unfortunately new to node and running into some confusion regarding the asynchronous/synchronous execution of node. I am using node, sequelize with sqlite and async.js. I have a series of Articles , each of which has a number of Authors . For each Authors in each Article , I'd like to check if the Author exists. If not, create it. The problem is, on the initial run, duplicate authors are being created, I assume due to asynchronous functionality causing an issue with checking for existence. For example, with the array: authors = ['A. Test', 'B. Test', 'C. Test', 'A. Test'] and the code:

In Rails I can perform a simple ORM query for the number of Likes a model has: @records = Model .select( 'model.*' ) .select( 'count(likes.*) as likes_count' ) .joins( 'LEFT JOIN likes ON model.id = likes.model_id' ) .group( 'model.id' ) This generates the query: SELECT models.*, count(likes.*) as likes_count FROM "models" JOIN likes ON models.id = likes.model_id GROUP BY models.id In Node Sequelize, any attempt at doing something similar fails: return Model.findAll({ group: [ '"Model".id' ], attributes: ['id', [Sequelize.fn('count', Sequelize.col('"Likes".id')), 'likes_count']], include: [{