not work!

[zenithtekla]

I plugged in all your code, same test folder, tables structure, package.json and everything.
It is not working.
On connecting to localhost:3000/api/users , get and post, I get the following error:
TypeError: Cannot read property 'getDAO' of undefined

[pjanaya]

Hi @zenithtekla,

When I made this example I didn't fix the dependencies well enough. Could you try replacing the package.json file with this one?

{
  "name": "node-api",
  "main": "server.js",
  "dependencies": {
    "body-parser": "^1.6.3",
    "express": "^4.8.3",
    "mysql": "~2.5.0",
    "sequelize": "~1.7.0",
    "sequelize-restful": "~0.3.0"
  }
}

After that, run npm install again. Anyway, keep in mind that this example was created 2 years ago and the big dependency "sequelize" has changed a lot. I recommend this for formation purposes but for a production environment it would be a good idea to take a look into the latest versions for all the modules.

Let me know if this works, though :)

[zenithtekla]

Hi @pjanaya,
Thank you for your reply.

I tried with your suggestion and of course did npm install again (didn't wipe node_modules folder, I expected npm to take care of conflicts). I tested with Advance REST client :

Get /users and /projects work.
POST with payload, e.g. { name: "zetek", password : "pp" } shows success (status:200) but results in a new object without empty property. ,{"id":4,"name":"","password":""},{"id":5,"name":"","password":""}
PUT with http://localhost:3000/api/users/4 to try update a user to show my name but failed.
DELETE is fine.

I am currently viewing this resource as a simple way to implement into my NodeMySQL git repo where I have the models defined there and want to declare associations/relationships but I'm not sure about whether I define the relationships in the module(calibrates)/server/controller.js or in the model.js files. I like to keep 1 model Schema for each file.

Controllers file is where the models are called, as you can see from my repo. The relationship is kept simple, 1:1, not sure whether to define hasMany, foreignKey or BelongTo. That is because my app is now abstracted in many layers and complexity built up. I am new to Sequelize in general.

In the official Docs of Sequelize LINK, they suggests having associate object sit in classMethods in the definition of the Schema.

Do I have to do it that way or Can I declare association/relationship in the controller (wherever I call the models.User and models.Project to make their association and build the logic behind them?

One thing, I notice: sequelize-restful doesn't support ACL, userPolicy, session and intermittent callback. Something like : app.get('/users/:id', controller.invokePolicycallback, controller.read);

I very much appreciate the simplicity of this magic sequelize-restful and hope there is an update for more fit with its dependencies and latest Sequelize version. Much as I observe this repo with appreciation, I seek solution so I look at several other resources too: epilogue, GraphQL, GraphQL-Sequelize, SailsJS, Derby and Restify. Those resources vary in term of the extra luxury (learning time to familiarise, complexity, high abstraction,... might be overkill - use a hammer on a tiny nail,

considering the scale of my app is still tiny, pending addition of ACL support, Bluebird, Testing and Brunch (or down to Webpack) for a build tool.. still a lot of work remaining to engineer my app ).

[pjanaya]

Well, I've tried a clean installation with the package.json. I've sent you before and it seems to be working. I'm using Postman to test the API. I don't know what else could you try. I've updated the package.json in the master branch. You could try removing completely your folder and make a clean installation. Also the table, just to make sure that's not the problem. If still not work maybe give a try to Postman.

Some time ago I had to create a bigger project and I had to split the models and routes into different files, one per type of object. I created a project example but I never had time to elaborate a good tutorial about it. This is how the index.js for the models looked like.

    // Create the sequelize variable
    var sequelize = create_db();

    // Declare all the model names
    var models = [
      'User',
      'Project'
    ];

    // Import each model
    models.forEach(function(model) {
      module.exports[model] = sequelize.import(__dirname + '/' + model);
    });

    // Describe relationships between models
    (function(m) {
       m.Project.belongsTo(m.User);
    })(module.exports);

    // Export connection
    module.exports.sequelize = sequelize;

    function create_db(){
        var Sequelize = require('sequelize');

        // db config
        var env = "dev";
        var config = require('./database.json')[env];
        var password = config.password ? config.password : null;

        // initialize database connection
        var sequelize = new Sequelize(
            config.database,
            config.user,
            config.password,
            {
                logging: console.log,
                define: {
                    timestamps: false
                }
            }
        );

        return sequelize;
    }

This file is imported from the main server.js. I declare the different models at the beginning, then I import them from different files, and then I define their relationships. It was a really simple example project but maybe it gives you an idea.

Anyway, I don't think "sequelize-restful" is prepared for big scale or complex projects. Probably you're right looking into other libraries.

I wish you the best of lucks :)

[zenithtekla]

Hello,
Thank you for your follow-up reply. I greatly appreciate your input.

I have somewhat similar with the index.js file you posted. It uses the fs.readdirSync to catch filenames and feed as models names as suggested from Sequelize Docs and somewhere in an online article I read.

While you described the relationship this way:

// Describe relationships between models
    (function(m) {
       m.Project.belongsTo(m.User);
    })(module.exports);

My current index.js suggests using "associate" keyword in the individual model file.

If you, by chance, know how to describe relationships using such a keyword, please let me know.
My project app is simple, contains ECMS tables (link to my Git posted previously).

The relational tables if consolidated in MongoDB collection would be the following, much simplified, right? native object support, no hassle of luxurious, performance consuming JOIN and problem of wrapping relationships but unfortunately, SQL database is tightly used:

var Schema1 = new Schema({
  asset_number: String,
  last_cal: Date,
  schedule: Number,
  next_cal: Date,
  file: {
    data: Buffer,
    contentType: String
  },
  models: [{
    model: String,
    location: {
      id: Number,
      desc: String
    }
  }]
});

Problem is I saw in Sequelize there is an 'associate' keyword example somewhere but couldn't grab how to use it.

 var Schema = sequelize.define('ECMS_Main', {
      asset_number: {
        type: DataTypes.STRING(20),
        allowNull: false,
        unique: true
      },
      last_cal: DataTypes.DATE(),
      schedule: DataTypes.INTEGER(20),
      next_cal: DataTypes.DATE(),
      file: DataTypes.BLOB()
  },
  {
      timestamps: false,
      tableName: 'ECMS_main_table',
      freezeTableName: true,
      charset: 'utf8',
      collate: 'utf8_unicode_ci',
      // probably here, correct???
      associate: {
           // what and how to write in here? Do we have to write in both the siblings or parent and child models?
      }
  });