Using Composite Types in Sequelize
In PostgreSQL, a composite type is structured like a row or record, consisting of field names and their corresponding data types. Setting a Sequelize model as a composite type enables you to store complex and structured data in a single column.
This guide explains how to define a model type as a composite type in your Sequelize models and configure the schema migration to manage both the composite types and the Sequelize models as a single migration unit using Atlas.
Atlas support for Composite Types is available exclusively to Pro users. To use this feature, run:
atlas login
Getting started with Atlas and Sequelize
Before we continue to composite types, ensure you have installed the Atlas Sequelize Provider on your Sequelize project.
To set up, follow along the getting started guide for Sequelize and Atlas.
Composite Schema
The Sequelize models are mostly used for defining tables and interacting with the database. Composite types, or any other database objects do not have representation in Sequelize models - a composite type can be defined once, and may be used multiple times in different columns and models.
In order to extend our PostgreSQL schema to include both custom composite types and our Sequelize types, we configure Atlas to read the state of the schema from a Composite Schema data source. Follow the steps below to configure this for your project:
1. Create a schema.sql
that defines the necessary composite type. In the same way, you can configure the composite type in
Atlas Schema HCL language:
- Using SQL
- Using HCL
CREATE TYPE address AS (
street text,
city text
);
schema "public" {}
composite "address" {
schema = schema.public
field "street" {
type = text
}
field "city" {
type = text
}
}
2. In your Sequelize models, define a column that uses the composite type only in PostgreSQL dialect:
'use strict';
module.exports = function(sequelize, DataTypes) {
const address = {
type: 'address',
fields: [
'street',
'city',
],
};
const User = sequelize.define('User', {
name: {
type: DataTypes.STRING,
allowNull: false
},
address: address
});
return User;
};
3. In your atlas.hcl
config file, add a composite_schema
that includes both your custom types defined in
schema.sql
and your Sequelize models:
data "composite_schema" "app" {
# Load custom types first.
schema "public" {
url = "file://schema.sql"
}
schema "public" {
url = data.external_schema.sequelize.url
}
}
env "local" {
src = data.composite_schema.app.url
dev = "docker://postgres/15/dev?search_path=public"
}
Usage
After setting up our schema, we can get its representation using the atlas schema inspect
command, generate migrations for
it, apply them to a database, and more. Below are a few commands to get you started with Atlas:
Inspect the Schema
The atlas schema inspect
command is commonly used to inspect databases. However, we can also use it to inspect our
composite_schema
and print the SQL representation of it:
atlas schema inspect \
--env local \
--url env://src \
--format '{{ sql . }}'
The command above prints the following SQL. Note, the address
composite type is defined in the schema before
its usage in the address
field:
-- Create composite type "address"
CREATE TYPE "address" AS ("street" text, "city" text);
-- Create "Users" table
CREATE TABLE "Users" ("id" serial NOT NULL, "name" character varying(255) NOT NULL, "address" "address" NULL, "createdAt" timestamptz NOT NULL, "updatedAt" timestamptz NOT NULL, PRIMARY KEY ("id"));
Generate Migrations For the Schema
To generate a migration for the schema, run the following command:
atlas migrate diff \
--env local
Note that a new migration file is created with the following content:
-- Create composite type "address"
CREATE TYPE "address" AS ("street" text, "city" text);
-- Create "Users" table
CREATE TABLE "Users" ("id" serial NOT NULL, "name" character varying(255) NOT NULL, "address" "address" NULL, "createdAt" timestamptz NOT NULL, "updatedAt" timestamptz NOT NULL, PRIMARY KEY ("id"));
Apply the Migrations
To apply the migration generated above to a database, run the following command:
atlas migrate apply \
--env local \
--url "postgres://postgres:pass@localhost:5432/database?search_path=public&sslmode=disable"
Sometimes, there is a need to apply the schema directly to the database without generating a migration file. For example, when experimenting with schema changes, spinning up a database for testing, etc. In such cases, you can use the command below to apply the schema directly to the database:
atlas schema apply \
--env local \
--url "postgres://postgres:pass@localhost:5432/database?search_path=public&sslmode=disable"