I'm trying to join 3 tables together Products
, Suppliers
and Categories
and then get row with SupplierID = 13
. I have read How to implement many to many association in sequelize, there is explained how to associate 0:M
.
DB model:
Code:
var Sequelize = require('sequelize')
var sequelize = new Sequelize('northwind', 'nodejs', 'nodejs', {dialect: 'mysql',})
var Project = require('sequelize-import')(__dirname + '/models', sequelize, { exclude: ['index.js'] });
Project.Suppliers.hasMany(Project.Products, {foreignKey: 'SupplierID'});
Project.Products.belongsTo(Project.Suppliers, {foreignKey: 'SupplierID'});
Project.Categories.hasMany(Project.Products, {foreignKey: 'CategoryID'});
Project.Products.belongsTo(Project.Categories, {foreignKey: 'CategoryID'});
Project.Products
.find({
where: {
SupplierID: 13
},
include: [
Project.Suppliers,
Project.Category,
]
})
.success(function(qr){
if (qr == null) throw "Err";
console.log("---");
console.log(qr);
})
.error(function(err){
console.log("Err");
});
Log:
EventEmitter#success|ok is deprecated, please use promise-style instead.
EventEmitter#failure|fail|error is deprecated, please use promise-style instead.
Err
Creating associations in sequelize is done by calling one of the belongsTo / hasOne / hasMany / belongsToMany functions on a model (the source), and providing another model as the first argument to the function (the target). hasOne - adds a foreign key to the target and singular association mixins to the source.
Because of this, it possesses all the required functions for working with servers, HTML, and databases, minimizing the need for JS code on your front-end. Winner: Node. js wins the Node. js vs PHP performance battle as it offers better speed and a seamless and concurrent experience both for the developer and end-user.
Node. js programs can be slow due to a CPU/IO-bound operation, such as a database query or slow API call. For most Node. js applications, data fetching is done via an API request and a response is returned.
Update: 15 Jan 15 - added .finally()
handler. Also indicated how .then()
is being fed with an argument from the previous handler and how to perform the next sequenced query.
The .success
, .error
and .done
handlers are deprecated. The errors are not critical and it is likely that backwards compatibility will be maintained on them. But you should still change it.
As per promise A specs: http://wiki.commonjs.org/wiki/Promises/A
You now should do the following style:
db.Model.find(something)
.then(function(results) {
//do something with results
//you can also take the results to make another query and return the promise.
return db.anotherModel.find(results[0].anotherModelId);
}).then(function(results) {
//do something else
}).catch(function(err) {
console.log(err);
}).finally(function() {
// finally gets called always regardless of
// whether the promises resolved with or without errors.
// however this finally handler does not receive any arguments.
});
In short:
Use .then
instead of .success
Use .catch
instead of .error
Use .finally
instead of .done
*note: .finally
will always get called regardless.
i had the same issue with you, you can change .success
and .error
with single .done(function(err, result))
to do both operation and the warning message disappear too.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With