This project conforms to the specification laid out in the jsonapi-server handler documentation.
- Postgres (>= 9.4)
var SQLStore = ;jsonApi;
logging property controls the logging of the emitted SQL and can either be
false (which will mean it will be captured by the internal debugging module under the namespace
jsonApi:store:relationaldb:sequelize) or a user provided function (e.g.
console.log) to which a string containing the information to be logged will be passed as the first argument.
Alternative Usage - Provide Sequelize instance
If you are already using sequelize or need to have access to the sequelize instance, you may provide an instance to the store to be used instead of having the store create a new instance from the given config.
var RelationalDbStore = ;var Sequelize = ;var sequelize = "jsonapi" "root" null dialect: "mysql";jsonApi;
- Search, Find, Create, Delete, Update
- Efficient lookups via appropriate indexes
- Filtering happens at the database layer
- Transactional queries
Getting to Production
Getting this data store to production isn't too bad...
- Bring up your relational database stack.
- Create the database(s).
- Create the database tables. You can call
(new SQLStore()).populate()to have this module attempt to create the require tables. If you enable debugging via
DEBUG=jsonApi:store:*you'll see the create-table statements - you can target a local database, call populate(), grab the queries, review them and finally run them against your production stack manually.
- Deploy your code.
When deploying schema changes, you'll need to correct your database schema - database migrations are left as an exercise for the user. If your schema are likely to change frequently, maybe consider using a different (less schema-driven) data store.
When changing columns in a production database, a typical approach might be to create a new table that is a clone of the table in production, copy all data from the production table into the new table, run an ALTER-TABLE command on the new table to adjust the columns (this may take a while and will lock the table), then run a RENAME-TABLES to swap the production table out for the new one.
Note: When populating database tables, you can use the
force config option to DROP and CREATE tables. This is helpful in development stage, when your data doesn't matter and you want your Tables schemas to change according to the DAOs without having to manually write migrations.
Relational databases don't differentiate between
Joi does differentiate between
null values. Some
undefined properties will pass validation, whilst
null properties may not. For example, the default articles resource contains a
created attribute of type
"date" - this won't pass validation with a
null value, so the Joi schema will need tweaking.