使用Sequelize向PostgreSQL导入JSON种子数据时出错

It looks like you’re hitting an error because your Report model doesn’t have a dedicated field to store that JSON analytics configuration object you’re trying to seed. Let’s break down how to fix this:

Common Causes of the Error #

• Your model is missing a column defined with a JSON-compatible data type to hold the viewId, dateRanges, samplingLevel, etc., data.
• If you do have a field, it’s probably set to STRING or another non-JSON type, which can’t parse the object you’re passing.

Step-by-Step Solution #

1. Update Your Report Model #

First, add a new field to your model that supports JSON data. Depending on your database, use DataTypes.JSON (works across most databases) or DataTypes.JSONB (PostgreSQL-specific, offers better querying capabilities). Here’s how your updated model might look:

module.exports = (Sequelize, DataTypes) => {
  const Report = Sequelize.define('Report', {
    name: {
      type: DataTypes.STRING,
      allowNull: false,
      unique: true // Assuming this was the cut-off part of your code
    },
    analyticsConfig: { // New field to store your JSON data
      type: DataTypes.JSON,
      allowNull: true // Set to false if this field is required
    }
    // Add any other existing fields here
  }, {
    // Model options like timestamps or table name go here
  });

  return Report;
};

2. Create and Run a Migration (If Needed) #

If your Reports table already exists in the database, you’ll need a migration to add the new column:

sequelize migration:generate --name add-analytics-config-to-reports

Edit the generated migration file to add the column:

'use strict';

module.exports = {
  async up(queryInterface, Sequelize) {
    await queryInterface.addColumn('Reports', 'analyticsConfig', {
      type: Sequelize.JSON,
      allowNull: true
    });
  },

  async down(queryInterface, Sequelize) {
    await queryInterface.removeColumn('Reports', 'analyticsConfig');
  }
};

Run the migration with:

sequelize db:migrate

3. Adjust Your Seed File #

Make sure your seed file passes the JSON object into the correct field. Example seed code:

'use strict';

module.exports = {
  async up(queryInterface, Sequelize) {
    await queryInterface.bulkInsert('Reports', [{
      name: 'Sample Channel Grouping Report',
      analyticsConfig: { 
        viewId: null, 
        dateRanges: [ { startDate: null, endDate: null } ], 
        samplingLevel: 'DEFAULT', 
        dimensions: [ { name: 'ga:channelGrouping' } ], 
        metrics: [ { expression: 'ga:users' } ] 
      },
      createdAt: new Date(),
      updatedAt: new Date()
    }], {});
  },

  async down(queryInterface, Sequelize) {
    await queryInterface.bulkDelete('Reports', null, {});
  }
};

4. Re-Run the Seed Command #

Now try running the seed command again:

sequelize db:seed:all

Additional Tips #

• If you’re using PostgreSQL, consider JSONB instead of JSON if you plan to query the contents of the JSON field later.
• If analyticsConfig should never be null, set allowNull: false in both the model and migration, and ensure your seed data has a valid JSON object (even if nested values are null).
• Double-check that field names in your seed file match exactly with your model’s column names (case-sensitive depending on your database setup).

内容的提问来源于stack exchange，提问作者Jaygles