tachybase_todo/docs/en-US/api/database/index.md

Database

Overview

Database is the database interaction tool provided by NocoBase, it provides very convenient database interaction features for no-code and low-code applications. The supported databases are:

• SQLite 3.8.8+
• MySQL 8.0.17+
• PostgreSQL 10.0+

Connect to Database

In Database constructor, database connection can be configured by passing the options parameter.

const { Database } = require('@nocobase/database');

// SQLite database configuration parameters
const database = new Database({
  dialect: 'sqlite',
  storage: 'path/to/database.sqlite'
})

// MySQL \ PostgreSQL database configuration parameters
const database = new Database({
  dialect: /* 'postgres' or 'mysql' */,
  database: 'database',
  username: 'username',
  password: 'password',
  host: 'localhost',
  port: 'port'
})

Refer to Constructor for detailed configurations.

Define Data Structure

Database defines database structure through Collection, one Collection object represents one table in the database.

// Define Collection 
const UserCollection = database.collection({
  name: 'users',
  fields: [
    {
      name: 'name',
      type: 'string',
    },
    {
      name: 'age',
      type: 'integer',
    },
  ],
});

After the database structure is defined, use sync() method to synchronize the database structure.

await database.sync();

Refer to Collection for detailed usage of Collection.

CRUD Data

Database operates data through Repository.

const UserRepository = UserCollection.repository();

// Create
await UserRepository.create({
  name: 'Mark',
  age: 18,
});

// Query
const user = await UserRepository.findOne({
  filter: {
    name: 'Mark',
  },
});

// Update
await UserRepository.update({
  values: {
    age: 20,
  },
});

// Delete
await UserRepository.destroy(user.id);

Refer to Repository for details of data CRUD.

Constructor

Signature

• constructor(options: DatabaseOptions)

Create a database instance.

Parameter

Name	Type	Default	Description
options.host	string	'localhost'	Database host
options.port	number	-	Database service port, there is a default port depending on the database used
options.username	string	-	Database username
options.password	string	-	Database password
options.database	string	-	Database name
options.dialect	string	'mysql'	Database type
options.storage?	string	':memory:'	Storage mode for SQLite
options.logging?	boolean	false	Whether to enable logging
options.define?	Object	{}	Default table definition parameters
options.tablePrefix?	string	''	NocoBase extension, table prefix
options.migrator?	UmzugOptions	{}	NocoBase extension, parameters for migrator, refer to Umzug for the implementation

Migration Methods

addMigration()

Add single migration file.

Signature

• addMigration(options: MigrationItem)

Parameter

Name	Type	Default	Description
options.name	string	-	Name of the migration file
options.context?	string	-	Context of the migration file
options.migration?	typeof Migration	-	Custom type of the migration file
options.up	Function	-	up method of the migration file
options.down	Function	-	down method of the migration file

Example

db.addMigration({
  name: '20220916120411-test-1',
  async up() {
    const queryInterface = this.context.db.sequelize.getQueryInterface();
    await queryInterface.query(/* your migration sqls */);
  }
});

addMigrations()

Add the migration files in the specified directory.

Signature

• addMigrations(options: AddMigrationsOptions): void

Parameter

Name	Type	Default	Description
options.directory	string	''	Directory where the migration files are located
options.extensions	string[]	['js', 'ts']	File extensions
options.namespace?	string	''	Namespace
options.context?	Object	{ db }	Context of the migration files

Example

db.addMigrations({
  directory: path.resolve(__dirname, './migrations'),
  namespace: 'test'
});

Tool Methods

inDialect()

Check whether the current database type is the specified type.

Signature

• inDialect(dialect: string[]): boolean

Parameter

Name	Type	Default	Description
dialect	string[]	-	Database type, options are mysql, postgres and sqlite

getTablePrefix()

Get the table name prefix in the configuration.

Signature

• getTablePrefix(): string

Data Table Configuration

collection()

Define a data table. This is similar to the define method of Sequelize, which only creates table structure in memory. Call the sync method if it is needed to be persisted to the database.

Signature

• collection(options: CollectionOptions): Collection

Parameter

All configuration parameters of options is consistent with the constructor of the Collection class, refer to Collection.

Event

• 'beforeDefineCollection': Trigger before defining the table.
• 'afterDefineCollection': Trigger after defining the table.

Example

db.collection({
  name: 'books',
  fields: [
    {
      type: 'string',
      name: 'title',
    },
    {
      type: 'float',
      name: 'price',
    }
  ]
});

// sync collection as table to db
await db.sync();

getCollection()

Gets a defined data table.

Signature

• getCollection(name: string): Collection

Parameter

Name	Type	Default	Description
name	string	-	Table name

Example

const collection = db.getCollection('books');

hasCollection()

Check whether if a specified data table has been defined.

Signature

• hasCollection(name: string): boolean

Parameter

Name	Type	Default	Description
name	string	-	Table name

Example

db.collection({ name: 'books' });

db.hasCollection('books'); // true

db.hasCollection('authors'); // false

removeCollection()

Remove a defined data table; remove from memory only. Call the sync method if it is needed to be persisted to the database.

Signature

• removeCollection(name: string): void

Parameter

Name	Type	Default	Description
name	string	-	Table name

Event

• 'beforeRemoveCollection': Trigger before removing the table.
• 'afterRemoveCollection': Trigger after removing the table

Example

db.collection({ name: 'books' });

db.removeCollection('books');

import()

Load all files in the import file directory into memory as the configuration of collection.

Signature

• async import(options: { directory: string; extensions?: ImportFileExtension[] }): Promise<Map<string, Collection>>

Parameter

Name	Type	Default	Description
options.directory	string	-	Path of directory to be imported
options.extensions	string[]	['ts', 'js']	Scan for specific suffixes

Example

The collection defined by file ./collections/books.ts is as below:

export default {
  name: 'books',
  fields: [
    {
      type: 'string',
      name: 'title',
    }
  ]
};

Import the relevant configurations when loading the plugin:

class Plugin {
  async load() {
    await this.app.db.import({
      directory: path.resolve(__dirname, './collections'),
    });
  }
}

Extended Registration and Acquisition

registerFieldTypes()

Register custom field type.

Signature

• registerFieldTypes(fieldTypes: MapOf<typeof Field>): void

Parameter

fieldTypes is a key-value pair, where key is the field type name and value is the field type class.

Example

import { Field } from '@nocobase/database';

class MyField extends Field {
  // ...
}

db.registerFieldTypes({
  myField: MyField,
});

registerModels()

Register custom data model class.

Signature

• registerModels(models: MapOf<ModelStatic<any>>): void

Parameter

models is a key-value pair, where key is the data model name and value is the data model class.

Example

import { Model } from '@nocobase/database';

class MyModel extends Model {
  // ...
}

db.registerModels({
  myModel: MyModel,
});

db.collection({
  name: 'myCollection',
  model: 'myModel'
});

registerRepositories()

Register custom data repository class.

Signature

• registerRepositories(repositories: MapOf<RepositoryType>): void

Parameter

repositories is a key-value pair, where key is the data repository name and value is the data repository class.

Example

import { Repository } from '@nocobase/database';

class MyRepository extends Repository {
  // ...
}

db.registerRepositories({
  myRepository: MyRepository,
});

db.collection({
  name: 'myCollection',
  repository: 'myRepository'
});

registerOperators()

Register custom data query operator.

Signature

• registerOperators(operators: MapOf<OperatorFunc>)

Parameter

operators is a key-value pair, where key is the operator name and value is the generating function of the comparison operator statement.

Example

db.registerOperators({
  $dateOn(value) {
    return {
      [Op.and]: [{ [Op.gte]: stringToDate(value) }, { [Op.lt]: getNextDay(value) }],
    };
  }
});

db.getRepository('books').count({
  filter: {
    createdAt: {
      // registered operator
      $dateOn: '2020-01-01',
    }
  }
});

getModel()

Get the defined data model class. If no custom model class has been registered before, the default model class of Sequelize will be returned. The default name is the same as the name defined by collection.

Signature

• getModel(name: string): Model

Parameter

Name	Type	Default	Description
name	string	-	Registered model name

Example

db.registerModels({
  books: class MyModel extends Model {}
});

const ModelClass = db.getModel('books');

console.log(ModelClass.prototype instanceof MyModel) // true

Note: The model class retrieved from collection is not strictly equivalent to the model class at registration, but is inherited from the model class at registration. Since the properties of Sequelize's model class are modified during initialization, NocoBase automatically handles this inheritance relationship. All thr definitions work fine except that the classes are not equal.

getRepository()

Get the defined data repository class. If no custom data repository class has been registered before, the default data repository class of NocoBase will be returned. The default name is the same as the name defined by collection.

Data repository class is mainly used for the CRUD operations based on data model, refer to Repository.

Signature

• getRepository(name: string): Repository
• getRepository(name: string, relationId?: string | number): Repository

Parameter

Name	Type	Default	Description
name	string	-	Registered data repository name
relationId	string | number	-	Foreign key value for relational data

When the name contains relationship in the form of 'tables.relactions', the related data repository class is returned. If the second parameter is provided, the data repository will be used (query, modify, etc.) based on the foreign key values of the relational data.

Example

Suppose there are two data tables posts and authors, and there is a foreign key in the posts table points to the authors table:

const AuthorsRepo = db.getRepository('authors');
const author1 = AuthorsRepo.create({ name: 'author1' });

const PostsRepo = db.getRepository('authors.posts', author1.id);
const post1 = AuthorsRepo.create({ title: 'post1' });
asset(post1.authorId === author1.id); // true

Database Event

on()

Listen for database events.

Signature

• on(event: string, listener: (...args: any[]) => void | Promise<void>): void

Parameter

Name	Type	Default	Description
event	string	-	Event name
listener	Function	-	Event listener

Event name supports Model event of Sequelize by default. Global event is listened to by the name <sequelize_model_global_event>, single Model event is listened to by the name <model_name>. <sequelize_model_event>.

Refer to the Built-in Events section for parameter descriptions and detailed examples of all built-in event types.

off()

Remove the event listener function.

Signature

• off(name: string, listener: Function)

Parameter

Name	Type	Default	Description
name	string	-	Event name
listener	Function	-	Event listener

Example

const listener = async (model, options) => {
  console.log(model);
};

db.on('afterCreate', listener);

db.off('afterCreate', listener);

Database Operation

auth()

Database connection verification. It can be used to ensure that the application has established connection to the data.

Signature

• auth(options: QueryOptions & { retry?: number } = {}): Promise<boolean>

Parameter

Name	Type	Default	Description
options?	Object	-	Verification option
options.retry?	number	10	Number of retries in case of verification failure
options.transaction?	Transaction	-	Transaction object
options.logging?	boolean | Function	false	Whether to print the log

Example

await db.auth();

reconnect()

Reconnect to the database.

Example

await db.reconnect();

closed()

Check whether database has closed the connection.

Signature

• closed(): boolean

close()

Closes database connection. Equivalent to sequelize.close().

sync()

Synchronizes database table structure. Equivalent to sequelize.sync(), refer to Sequelize documentation for parameters.

clean()

Empty the database, it will delete all data tables.

Signature

• clean(options: CleanOptions): Promise<void>

Parameter

Name	Type	Default	Description
options.drop	boolean	false	Whether to remove all data tables
options.skip	string[]	-	Names of tables to skip
options.transaction	Transaction	-	Transaction object

Example

Removes all tables except for the users table.

await db.clean({
  drop: true,
  skip: ['users']
})

Package-Level Export

defineCollection()

Create the configuration content of a data table.

Signature

• defineCollection(name: string, config: CollectionOptions): CollectionOptions

Parameter

Name	Type	Default	Description
collectionOptions	CollectionOptions	-	All parameters are the same with db.collection()

Example

For the data table configuration file to be imported by db.import():

import { defineCollection } from '@nocobase/database';

export default defineCollection({
  name: 'users',
  fields: [
    {
      type: 'string',
      name: 'name',
    },
  ],
});

extendCollection()

扩展已在内存中的表结构配置内容，主要用于 import() 方法导入的文件内容。该方法是 @nocobase/database 包导出的顶级方法，不通过 db 实例调用。也可以使用 extend 别名。

签名

• extendCollection(collectionOptions: CollectionOptions, mergeOptions?: MergeOptions): ExtendedCollectionOptions

参数

参数名	类型	默认值	描述
collectionOptions	CollectionOptions	-	与所有 db.collection() 的参数相同
mergeOptions?	MergeOptions	-	npm 包 deepmerge 的参数

示例

原始 books 表定义（books.ts）：

export default {
  name: 'books',
  fields: [
    { name: 'title', type: 'string' }
  ]
}

扩展 books 表定义（books.extend.ts）：

import { extend } from '@nocobase/database';

// 再次扩展
export default extend({
  name: 'books',
  fields: [
    { name: 'price', type: 'number' }
  ]
});

以上两个文件如在调用 import() 时导入，通过 extend() 再次扩展以后，books 表将拥有 title 和 price 两个字段。

此方法在扩展已有插件已定义的表结构时非常有用。

内置事件

数据库会在相应的生命周期触发以下对应的事件，通过 on() 方法订阅后进行特定的处理可满足一些业务需要。

'beforeSync' / 'afterSync'

当新的表结构配置（字段、索引等）被同步到数据库前后触发，通常在执行 collection.sync()（内部调用）时会触发，一般用于一些特殊的字段扩展的逻辑处理。

签名

on(eventName: `${string}.beforeSync` | 'beforeSync' | `${string}.afterSync` | 'afterSync', listener: SyncListener): this

类型

import type { SyncOptions, HookReturn } from 'sequelize/types';

type SyncListener = (options?: SyncOptions) => HookReturn;

示例

const users = db.collection({
  name: 'users',
  fields: [
    { type: 'string', name: 'username' }
  ]
});

db.on('beforeSync', async (options) => {
  // do something
});

db.on('users.afterSync', async (options) => {
  // do something
});

await users.sync();

'beforeValidate' / 'afterValidate'

创建或更新数据前会有基于 collection 定义的规则对数据的验证过程，在验证前后会触发对应事件。当调用 repository.create() 或 repository.update() 时会触发。

签名

on(eventName: `${string}.beforeValidate` | 'beforeValidate' | `${string}.afterValidate` | 'afterValidate', listener: ValidateListener): this

类型

import type { ValidationOptions } from 'sequelize/types/lib/instance-validator';
import type { HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

type ValidateListener = (model: Model, options?: ValidationOptions) => HookReturn;

示例

db.collection({
  name: 'tests',
  fields: [
    {
      type: 'string',
      name: 'email',
      validate: {
        isEmail: true,
      },
    }
  ],
});

// all models
db.on('beforeValidate', async (model, options) => {
  // do something
});
// tests model
db.on('tests.beforeValidate', async (model, options) => {
  // do something
});

// all models
db.on('afterValidate', async (model, options) => {
  // do something
});
// tests model
db.on('tests.afterValidate', async (model, options) => {
  // do something
});

const repository = db.getRepository('tests');
await repository.create({
  values: {
    email: 'abc', // checks for email format
  },
});
// or 
await repository.update({
  filterByTk: 1,
  values: {
    email: 'abc', // checks for email format
  },
});

'beforeCreate' / 'afterCreate'

创建一条数据前后会触发对应事件，当调用 repository.create() 时会触发。

签名

on(eventName: `${string}.beforeCreate` | 'beforeCreate' | `${string}.afterCreate` | 'afterCreate', listener: CreateListener): this

类型

import type { CreateOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type CreateListener = (model: Model, options?: CreateOptions) => HookReturn;

示例

db.on('beforeCreate', async (model, options) => {
  // do something
});

db.on('books.afterCreate', async (model, options) => {
  const { transaction } = options;
  const result = await model.constructor.findByPk(model.id, {
    transaction
  });
  console.log(result);
});

'beforeUpdate' / 'afterUpdate'

更新一条数据前后会触发对应事件，当调用 repository.update() 时会触发。

签名

on(eventName: `${string}.beforeUpdate` | 'beforeUpdate' | `${string}.afterUpdate` | 'afterUpdate', listener: UpdateListener): this

类型

import type { UpdateOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type UpdateListener = (model: Model, options?: UpdateOptions) => HookReturn;

示例

db.on('beforeUpdate', async (model, options) => {
  // do something
});

db.on('books.afterUpdate', async (model, options) => {
  // do something
});

'beforeSave' / 'afterSave'

创建或更新一条数据前后会触发对应事件，当调用 repository.create() 或 repository.update() 时会触发。

签名

on(eventName: `${string}.beforeSave` | 'beforeSave' | `${string}.afterSave` | 'afterSave', listener: SaveListener): this

类型

import type { SaveOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type SaveListener = (model: Model, options?: SaveOptions) => HookReturn;

示例

db.on('beforeSave', async (model, options) => {
  // do something
});

db.on('books.afterSave', async (model, options) => {
  // do something
});

'beforeDestroy' / 'afterDestroy'

删除一条数据前后会触发对应事件，当调用 repository.destroy() 时会触发。

签名

on(eventName: `${string}.beforeDestroy` | 'beforeDestroy' | `${string}.afterDestroy` | 'afterDestroy', listener: DestroyListener): this

类型

import type { DestroyOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type DestroyListener = (model: Model, options?: DestroyOptions) => HookReturn;

示例

db.on('beforeDestroy', async (model, options) => {
  // do something
});

db.on('books.afterDestroy', async (model, options) => {
  // do something
});

'afterCreateWithAssociations'

创建一条携带层级关系数据的数据之后会触发对应事件，当调用 repository.create() 时会触发。

签名

on(eventName: `${string}.afterCreateWithAssociations` | 'afterCreateWithAssociations', listener: CreateWithAssociationsListener): this

类型

import type { CreateOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type CreateWithAssociationsListener = (model: Model, options?: CreateOptions) => HookReturn;

示例

db.on('afterCreateWithAssociations', async (model, options) => {
  // do something
});

db.on('books.afterCreateWithAssociations', async (model, options) => {
  // do something
});

'afterUpdateWithAssociations'

更新一条携带层级关系数据的数据之后会触发对应事件，当调用 repository.update() 时会触发。

签名

on(eventName: `${string}.afterUpdateWithAssociations` | 'afterUpdateWithAssociations', listener: CreateWithAssociationsListener): this

类型

import type { UpdateOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type UpdateWithAssociationsListener = (model: Model, options?: UpdateOptions) => HookReturn;

示例

db.on('afterUpdateWithAssociations', async (model, options) => {
  // do something
});

db.on('books.afterUpdateWithAssociations', async (model, options) => {
  // do something
});

'afterSaveWithAssociations'

创建或更新一条携带层级关系数据的数据之后会触发对应事件，当调用 repository.create() 或 repository.update() 时会触发。

签名

on(eventName: `${string}.afterSaveWithAssociations` | 'afterSaveWithAssociations', listener: SaveWithAssociationsListener): this

类型

import type { SaveOptions, HookReturn } from 'sequelize/types';
import type { Model } from '@nocobase/database';

export type SaveWithAssociationsListener = (model: Model, options?: SaveOptions) => HookReturn;

示例

db.on('afterSaveWithAssociations', async (model, options) => {
  // do something
});

db.on('books.afterSaveWithAssociations', async (model, options) => {
  // do something
});

'beforeDefineCollection'

当定义一个数据表之前触发，如调用 db.collection() 时。

注：该事件是同步事件。

签名

on(eventName: 'beforeDefineCollection', listener: BeforeDefineCollectionListener): this

类型

import type { CollectionOptions } from '@nocobase/database';

export type BeforeDefineCollectionListener = (options: CollectionOptions) => void;

示例

db.on('beforeDefineCollection', (options) => {
  // do something
});

'afterDefineCollection'

当定义一个数据表之后触发，如调用 db.collection() 时。

注：该事件是同步事件。

签名

on(eventName: 'afterDefineCollection', listener: AfterDefineCollectionListener): this

类型

import type { Collection } from '@nocobase/database';

export type AfterDefineCollectionListener = (options: Collection) => void;

示例

db.on('afterDefineCollection', (collection) => {
  // do something
});

'beforeRemoveCollection' / 'afterRemoveCollection'

当从内存中移除一个数据表前后触发，如调用 db.removeCollection() 时。

注：该事件是同步事件。

签名

on(eventName: 'beforeRemoveCollection' | 'afterRemoveCollection', listener: RemoveCollectionListener): this

类型

import type { Collection } from '@nocobase/database';

export type RemoveCollectionListener = (options: Collection) => void;

示例

db.on('beforeRemoveCollection', (collection) => {
  // do something
});

db.on('afterRemoveCollection', (collection) => {
  // do something
});