Since the release of v1.6.0
in April 2013, many new features have
been added to Sequelize. This was mostly possible due to the great
help of the community. Furthermore Daniel Durante
joined us in May, who is a big help everyday and will be glad to help
everyone who joins our IRC channel.
This post is about the features, that have been added since April
and that are currently available in the current NPM package v1.7.0-alpha2
.
After 552 commits, almost 8 months of work, 42 relevant changes and the acquisition of two more core contributors since the last stable version, we finally published Sequelize v1.6.0 to NPM today. With this release, we’ve been adding some important and often requested features, as well as making things more stable while improving the performance noticeably. However, we know that there are a lot of important features missing, so we created a rough roadmap, which should make plans clearer and which will assist us in taking the right way. Also, every repository which was somehow related to Sequelize, has been moved to a Github organization.
Sequelize v1.4.1 was released on May 3rd, 2012. Major changes are deprecation of Node.JS < v0.6.0, the possibility of selective saves, some additions to the sequelize binary, a often requested complete function for asynchronous progresses, as well as the chance to customize the logging strategy.
Sequelize v1.4.0 was released in April 2012. Besides some
important bugfixes, the new version shipped also major improvements
as support for PostgreSQL, compatibility to JSON.stringify
,
connection pooling for MySQL, the possibility to set a date’s default
value to the current date, as well as the chance to customize the logging strategy.
Sequelize v1.3.0 was just released and comes with some funky new features and some minor refactorings, which you should know about. Most important things are: Migrations, validations, cross-database support and new event-listener notation.
This post summarizes changes in Sequelize v1.2.1. It is highly recommended to read this post due to some changes in default values and interfaces. There are also some minor, but very cool new features.