bookshelf vs knex vs sequelize vs typeorm
Node.js ORMライブラリ
bookshelfknexsequelizetypeorm類似パッケージ:

Node.js ORMライブラリ

ORM(Object-Relational Mapping)ライブラリは、データベースとアプリケーション間のデータのやり取りを簡素化するためのツールです。これにより、開発者はSQLクエリを直接書くことなく、オブジェクト指向の方法でデータベース操作を行うことができます。これらのライブラリは、データベースのスキーマをモデルとして定義し、データの取得、挿入、更新、削除を容易にします。

npmのダウンロードトレンド

3 年

GitHub Starsランキング

統計詳細

パッケージ
ダウンロード数
Stars
サイズ
Issues
公開日時
ライセンス
bookshelf06,357-2386年前MIT
knex020,266916 kB7063日前MIT
sequelize030,3482.91 MB1,0272ヶ月前MIT
typeorm036,47020.8 MB5175ヶ月前MIT

機能比較: bookshelf vs knex vs sequelize vs typeorm

データベースサポート

  • bookshelf:

    Bookshelfは、PostgreSQL、MySQL、SQLiteなどの一般的なリレーショナルデータベースをサポートしています。

  • knex:

    Knexは、PostgreSQL、MySQL、SQLite、Oracleなど、さまざまなデータベースをサポートしており、クエリビルダーとしても機能します。

  • sequelize:

    Sequelizeは、PostgreSQL、MySQL、MariaDB、SQLite、Microsoft SQL Serverなど、複数のデータベースをサポートしています。

  • typeorm:

    TypeORMは、PostgreSQL、MySQL、MariaDB、SQLite、Microsoft SQL Server、Oracleなど、広範なデータベースをサポートしています。

APIのシンプルさ

  • bookshelf:

    Bookshelfは、シンプルで直感的なAPIを提供しており、リレーショナルデータベースの操作が容易です。

  • knex:

    Knexは、クエリビルダーとしての柔軟性を持ちながら、APIは比較的シンプルで、SQLに近い形でクエリを構築できます。

  • sequelize:

    Sequelizeは、強力な機能を持ちながらも、APIはやや複雑で、学習曲線が急になる可能性があります。

  • typeorm:

    TypeORMは、TypeScriptの型安全性を活かしたAPIを提供しており、オブジェクト指向プログラミングに慣れた開発者には使いやすいですが、初心者には少し難しいかもしれません。

トランザクション管理

  • bookshelf:

    Bookshelfは、トランザクション管理をサポートしていますが、Knexを使用してトランザクションを明示的に管理する必要があります。

  • knex:

    Knexは、トランザクションを簡単に管理できる機能を提供しており、複雑なデータベース操作に対応できます。

  • sequelize:

    Sequelizeは、トランザクション管理が組み込まれており、複数の操作を一つのトランザクションとして処理することができます。

  • typeorm:

    TypeORMは、トランザクション管理をサポートしており、エンティティの操作をトランザクションとしてまとめることができます。

学習曲線

  • bookshelf:

    Bookshelfは、シンプルなAPIを持っているため、学習曲線は緩やかです。

  • knex:

    Knexは、SQLに近い構文を持つため、SQLに慣れている開発者には比較的学びやすいです。

  • sequelize:

    Sequelizeは、機能が豊富なため、学習曲線が急で、特に初心者には難しいかもしれません。

  • typeorm:

    TypeORMは、TypeScriptを使用するため、TypeScriptに慣れている開発者には学びやすいですが、初めての方には少し難しいかもしれません。

エコシステムとコミュニティ

  • bookshelf:

    Bookshelfは、Knexに依存しているため、Knexのエコシステムを活用できますが、他のORMに比べるとコミュニティは小さいです。

  • knex:

    Knexは、広範なエコシステムを持ち、多くのプラグインや拡張機能が利用可能です。

  • sequelize:

    Sequelizeは、非常に活発なコミュニティを持ち、多くのリソースやサポートが利用できます。

  • typeorm:

    TypeORMは、TypeScriptを使用する開発者に人気があり、活発なコミュニティと多くのリソースがあります。

選び方: bookshelf vs knex vs sequelize vs typeorm

  • bookshelf:

    Bookshelfは、Knex.jsを基盤として構築されているため、Knexを使用したい場合に最適です。また、シンプルなAPIを持ち、リレーショナルデータベースの操作を簡単に行いたい場合に適しています。

  • knex:

    Knexは、クエリビルダーとして使用されるため、SQLクエリを細かく制御したい場合に選択すべきです。データベースのスキーマを直接操作したい場合や、複雑なクエリを構築する必要がある場合に最適です。

  • sequelize:

    Sequelizeは、強力な機能を持つフル機能のORMであり、複数のデータベースをサポートしています。トランザクションやバリデーションなどの高度な機能が必要な場合に選ぶべきです。

  • typeorm:

    TypeORMは、TypeScriptとの統合が優れており、型安全性を重視するプロジェクトに最適です。エンティティベースのアプローチを採用しているため、オブジェクト指向プログラミングに慣れている開発者に適しています。

bookshelf のREADME

bookshelf.js

NPM Version Build Status Dependency Status devDependency Status

Bookshelf is a JavaScript ORM for Node.js, built on the Knex SQL query builder. It features both Promise-based and traditional callback interfaces, transaction support, eager/nested-eager relation loading, polymorphic associations, and support for one-to-one, one-to-many, and many-to-many relations.

It is designed to work with PostgreSQL, MySQL, and SQLite3.

Website and documentation. The project is hosted on GitHub, and has a comprehensive test suite.

Introduction

Bookshelf aims to provide a simple library for common tasks when querying databases in JavaScript, and forming relations between these objects, taking a lot of ideas from the Data Mapper Pattern.

With a concise, literate codebase, Bookshelf is simple to read, understand, and extend. It doesn't force you to use any specific validation scheme, and provides flexible, efficient relation/nested-relation loading and first-class transaction support.

It's a lean object-relational mapper, allowing you to drop down to the raw Knex interface whenever you need a custom query that doesn't quite fit with the stock conventions.

Installation

You'll need to install a copy of Knex, and either mysql, pg, or sqlite3 from npm.

$ npm install knex
$ npm install bookshelf

# Then add one of the following:
$ npm install pg
$ npm install mysql
$ npm install sqlite3

The Bookshelf library is initialized by passing an initialized Knex client instance. The Knex documentation provides a number of examples for different databases.

// Setting up the database connection
const knex = require('knex')({
  client: 'mysql',
  connection: {
    host     : '127.0.0.1',
    user     : 'your_database_user',
    password : 'your_database_password',
    database : 'myapp_test',
    charset  : 'utf8'
  }
})
const bookshelf = require('bookshelf')(knex)

// Defining models
const User = bookshelf.model('User', {
  tableName: 'users'
})

This initialization should likely only ever happen once in your application. As it creates a connection pool for the current database, you should use the bookshelf instance returned throughout your library. You'll need to store this instance created by the initialize somewhere in the application so you can reference it. A common pattern to follow is to initialize the client in a module so you can easily reference it later:

// In a file named, e.g. bookshelf.js
const knex = require('knex')(dbConfig)
module.exports = require('bookshelf')(knex)

// elsewhere, to use the bookshelf client:
const bookshelf = require('./bookshelf')

const Post = bookshelf.model('Post', {
  // ...
})

Examples

Here is an example to get you started:

const knex = require('knex')({
  client: 'mysql',
  connection: process.env.MYSQL_DATABASE_CONNECTION
})
const bookshelf = require('bookshelf')(knex)

const User = bookshelf.model('User', {
  tableName: 'users',
  posts() {
    return this.hasMany(Posts)
  }
})

const Post = bookshelf.model('Post', {
  tableName: 'posts',
  tags() {
    return this.belongsToMany(Tag)
  }
})

const Tag = bookshelf.model('Tag', {
  tableName: 'tags'
})

new User({id: 1}).fetch({withRelated: ['posts.tags']}).then((user) => {
  console.log(user.related('posts').toJSON())
}).catch((error) => {
  console.error(error)
})

Official Plugins

  • Virtuals: Define virtual properties on your model to compute new values.
  • Case Converter: Handles the conversion between the database's snake_cased and a model's camelCased properties automatically.
  • Processor: Allows defining custom processor functions that handle transformation of values whenever they are .set() on a model.

Community plugins

  • bookshelf-cascade-delete - Cascade delete related models on destroy.
  • bookshelf-json-columns - Parse and stringify JSON columns on save and fetch instead of manually define hooks for each model (PostgreSQL and SQLite).
  • bookshelf-mask - Similar to the functionality of the {@link Model#visible} attribute but supporting multiple scopes, masking models and collections using the json-mask API.
  • bookshelf-schema - A plugin for handling fields, relations, scopes and more.
  • bookshelf-signals - A plugin that translates Bookshelf events to a central hub.
  • bookshelf-paranoia - Protect your database from data loss by soft deleting your rows.
  • bookshelf-uuid - Automatically generates UUIDs for your models.
  • bookshelf-modelbase - An alternative to extend Model, adding timestamps, attribute validation and some native CRUD methods.
  • bookshelf-advanced-serialization - A more powerful visibility plugin, supporting serializing models and collections according to access permissions, application context, and after ensuring relations have been loaded.
  • bookshelf-plugin-mode - Plugin inspired by the functionality of the {@link Model#visible} attribute, allowing to specify different modes with corresponding visible/hidden fields of model.
  • bookshelf-secure-password - A plugin for easily securing passwords using bcrypt.
  • bookshelf-default-select - Enables default column selection for models. Inspired by the functionality of the {@link Model#visible} attribute, but operates on the database level.
  • bookshelf-ez-fetch - Convenient fetching methods which allow for compact filtering, relation selection and error handling.
  • bookshelf-manager - Model & Collection manager to make it easy to create & save deep, nested JSON structures from API requests.

Support

Have questions about the library? Come join us in the #bookshelf freenode IRC channel for support on knex.js and bookshelf.js, or post an issue on Stack Overflow.

Contributing

If you want to contribute to Bookshelf you'll usually want to report an issue or submit a pull-request. For this purpose the online repository is available on GitHub.

For further help setting up your local development environment or learning how you can contribute to Bookshelf you should read the Contributing document available on GitHub.

F.A.Q.

Can I use standard node.js style callbacks?

Yes, you can call .asCallback(function(err, resp) { on any database operation method and use the standard (err, result) style callback interface if you prefer.

My relations don't seem to be loading, what's up?

Make sure to check that the type is correct for the initial parameters passed to the initial model being fetched. For example new Model({id: '1'}).load([relations...]) will not return the same as new Model({id: 1}).load([relations...]) - notice that the id is a string in one case and a number in the other. This can be a common mistake if retrieving the id from a url parameter.

This is only an issue if you're eager loading data with load without first fetching the original model. new Model({id: '1'}).fetch({withRelated: [relations...]}) should work just fine.

My process won't exit after my script is finished, why?

The issue here is that Knex, the database abstraction layer used by Bookshelf, uses connection pooling and thus keeps the database connection open. If you want your process to exit after your script has finished, you will have to call .destroy(cb) on the knex property of your Bookshelf instance or on the Knex instance passed during initialization. More information about connection pooling can be found over at the Knex docs.

How do I debug?

If you pass debug: true in the options object to your knex initialize call, you can see all of the query calls being made. You can also pass that same option to all methods that access the database, like model.fetch() or model.destroy(). Examples:

// Turning on debug mode for all queries
const knex = require('knex')({
  debug: true,
  client: 'mysql',
  connection: process.env.MYSQL_DATABASE_CONNECTION
})
const bookshelf = require('bookshelf')(knex)

// Debugging a single query
new User({id: 1}).fetch({debug: true, withRelated: ['posts.tags']}).then(user => {
  // ...
})

Sometimes you need to dive a bit further into the various calls and see what all is going on behind the scenes. You can use node-inspector, which allows you to debug code with debugger statements like you would in the browser.

Bookshelf uses its own copy of the bluebird Promise library. You can read up here for more on debugging Promises.

Adding the following block at the start of your application code will catch any errors not otherwise caught in the normal Promise chain handlers, which is very helpful in debugging:

process.stderr.on('data', (data) => {
  console.log(data)
})

How do I run the test suite?

See the CONTRIBUTING document on GitHub.

Can I use Bookshelf outside of Node.js?

While it primarily targets Node.js, all dependencies are browser compatible, and it could be adapted to work with other javascript environments supporting a sqlite3 database, by providing a custom Knex adapter. No such adapter exists though.

Which open-source projects are using Bookshelf?

We found the following projects using Bookshelf, but there can be more:

  • Ghost (A blogging platform) uses bookshelf. [Link]
  • Soapee (Soap Making Community and Resources) uses bookshelf. [Link]
  • NodeZA (Node.js social platform for developers in South Africa) uses bookshelf. [Link]
  • Sunday Cook (A social cooking event platform) uses bookshelf. [Link]
  • FlyptoX (Open-source Node.js cryptocurrency exchange) uses bookshelf. [Link]
  • And of course, everything on here use bookshelf too.