No one attribute create by default in sequelize model

• If you want to ensure that only the attributes you have explicitly defined are added to your Sequelize model, without any automatic addition of default attributes like `id`, `createdAt`, `updatedAt`, or `deletedAt`, you can configure your model accordingly.

Here’s how you can achieve this:

• Disable Timestamps: To prevent Sequelize from automatically adding `createdAt` and `updatedAt` fields, you can set the `timestamps` option to `false` in your model's definition.

• Customize or Remove ID: If you do not want an auto-incrementing `id` field, you either define a custom primary key as explained previously or explicitly set an `id` attribute with `primaryKey: true` and manage its value manually. If your table schema does not require a primary key (which is very rare and generally not recommended), you could theoretically omit it, but this goes against best practices for relational database design.

• Disable Paranoid Feature: If you don't want the `deletedAt` column used for soft deletes, ensure you do not enable the `paranoid` option in your model definition.

• Here is an example configuration for a model where only the explicitly defined attributes are included, without any automatic attributes:

    const User = sequelize.define('User', {

        // Explicitly defined attributes here

        username: {

            type: DataTypes.STRING,

            allowNull: false

        },

        email: {

            type: DataTypes.STRING,

            unique: true,

            allowNull: false

        }

    }, {

        // Model configuration

        timestamps: false, // Disable createdAt and updatedAt

        // Note: By default, 'id' won't be added if we don't define it and don't have another primaryKey defined.

    });

• In this setup, the `User` model will only have `username` and `email` fields, without the default `id`, `createdAt`, `updatedAt`, or `deletedAt` fields.

• However, it is important to highlight that most relational databases require a primary key for each table for efficiency and integrity. The primary key ensures that each row in the table can be uniquely identified. Therefore, even if Sequelize allows you to omit the `id` field by not defining it and disabling timestamps, it's generally advisable to have a primary key defined for your tables.