Sequelize

Sequelize works on the principle of mapping database entries to JS objects and vice versa.

This is because JS objects are very well documented and JavaScript itself was modeled to deal with array structures much better than with SQL tables.

This enables a developer to manipulate a the data much easier in Node.js server-side environments, by using JavaScript instead of SQL commands.

Sequelize is quite advanced, supporting most operations supported by SQL engines, allowing an in-depth manipulation and processing of SQL data, just what developers have wanted from their ORMs.

Sequalize has been tested and seamlessly works with Express and Heroku-powered apps.

Currently supported databases:

MySQL

MSSQL

SQLite

PostgreSQL

MariaDB

What is new in this release:

• ADDED:
• It is now possible to defer constraints in PostgreSQL by added a property deferrable to the references object of a field.
• BUG:
• Fix an issue with the build in isIP validator returning false negatives

What is new in version 3.3.2:

• ADDED:
• It is now possible to defer constraints in PostgreSQL by added a property deferrable to the references object of a field.
• BUG:
• Fix an issue with the build in isIP validator returning false negatives

What is new in version 2.1.3:

• Bugs:
• Fixed issue with empty `include.where`
• Fixed issue with otherKey generation for self-association N:M

What is new in version 2.0.5:

• Bugs:
• Fixed issue with empty `include.where`
• Fixed issue with otherKey generation for self-association N:M

What is new in version 2.0.3:

• Bugs:
• Fixed issue with empty `include.where`
• Fixed issue with otherKey generation for self-association N:M

What is new in version 1.7.0:

• FEATURES:
• Covers more advanced include cases with limiting and filtering (specifically cases where a include would be in the subquery but its child include wouldnt be, for cases where a 1:1 association had a 1:M association as a nested include)
• BUG FIXES:
• Issue where connection would timeout before calling COMMIT resulting in data never reaching the database

What is new in version 1.5.0:

• Added possibility to globally disable adding of NULL values to SQL queries.
• Model.create can now also be used to specify values for mass assignment.
• QueryChainer will now provide the results of the added emitters in the order the emitters have been added.
• QueryChainer can now be initialized with serial items.
• Node 0.8 compatibility.
• Added options to hasMany getters.
• Pooling option is now correctly passed to PostgreSQL.

What is new in version 1.4.1:

• Added deprecation warning for node < v0.6.
• Added selective saving of instances.
• Added command to binary for creating a migration skeleton with current timestamp.
• Added complete function for each finder method.
• Fixed quotation for SQLite statements.
• Fixed timestamp parsing in migrations.

What is new in version 1.4.0:

• Fixed forced sync of many-to-many associations.
• Objects are now compatible JSON.stringify.
• When instantiating the sequelize object, you can now pass a function to logging. This allows you to customize the logging behavior. Default is now: console.log
• The default logging is still console.log but is wrapped after initialization as it crashes node < 0.6.x.
• PostgreSQL support.
• Connection-pooling for mysql.
• Added possibility to define NOW as default value for date data-types. Use Sequelize.NOW as defaultValue.

What is new in version 1.3.7:

• Fixed issue where multiple belongsTo or hasOne associations to the same table overwrite each other.

What is new in version 1.3.6:

• Don't update an existing updatedAt-attribute if timestamps option for a DAO is false.

What is new in version 1.3.4:

• Renamed Model/ModelFactory/ModelFactoryManager to DAO/DAOFactory/DAOFactoryManager
• npm test will run the test suite
• Documentation about setting up local development environment
• Removed updatedAt + createdAt from SequelizeMeta

What is new in version 1.3.3:

• Fixed sql-event emitter in all possible locations.

What is new in version 1.3.2:

• SQLite is now emitting the 'sql'-event as well.

What is new in version 1.3.0:

• REFACTORING:
• Model#all is now a function and not a getter.
• Renamed ModelDefinition to ModelFactory
• Private method scoping; Attributes are still public
• Use the new util module for node 0.6.2
• NEW FEATURE:
• QueryChainer can now run serially
• Association definition is chainable: Person.hasOne(House).hasMany(Address)
• Validations (Thanks to hiddentao)
• jQuery-like event listeners: .success(callback) and .error(callback)
• aliasing for select queries: Model.find({ where: 'id = 1', attributes: ['id', ['name', 'username']] }) ==> will return the user's name as username
• Cross-database support. currently supported: MySQL, SQLite
• Migrations
• TESTS:
• Removed all expresso tests and converted them to jasmine

What is new in version 1.2.1:

• Some changes in default values and interfaces.
• Renamed the global options for sync, query and define on sequelize; before: options.queryOptions; now: options.query.
• Allow definition of charset via global define option in sequelize or via charset option in sequelize.define.
• Allow definition of mysql engine via global define option in sequelize or via engine option in sequelize.define; default is InnoDB now.
• Find and findAll will now search in a list of values via: Model.findAll({where: { id: [1,2,3] }}); will return all models with id 1, 2 and 3
• Force latin1 charset for travis.

Requirements:

• JavaScript enabled on client side
• Node.js 0.6.21 or higher