Thanks for the report.
You don't need to supply a delimiter for postgres, it will just ignore it: Platform.schema('videoGames', '_'); => Platform.schema('videoGames');

Thanks for the tip... still learning. I'll try to figure out the fix too... I know it's in query-generator.js, but it looks pretty complicated.

This problem applies in several places:

• When checking if an enum already exists we should look in the right schema
• When creating a new enum it should be created in the right schema
• When referencing an enum in the table definition it should reference the right schema (maybe it should also be possible for users to specify another schema for the enum?)

I updated to 3.11.0 and still get errors
Unhandled rejection SequelizeDatabaseError: type "..._type" already exists

@marcingasior please show a reproducible test case then

if you use it from node cluster or restart 2 times your app
var Page = sequelize.define("page", {
id: {
type: DataTypes.UUID,
defaultValue: DataTypes.UUIDV4,
primaryKey: true,
allowNull: false
},
type: { type: DataTypes.ENUM('article','news','other') },
data: { type: DataTypes.JSON }
});

models.sequelize.sync().then(function () {

    var server = app.listen(app.get('port'), function() {
        log.info('Swagger API server listening on port ' + app.get('port'));
    });

});

@marcingasior Works fine for me, the second time it's run it finds the enum fine. Please create a SSCCE

Hi Jan,

I create a test and run it against local instance (9.3 and 9.4) and it looks it is working fine.

Thank you.