Adds CreatedAt and UpdatedAt fields in migration that don't exist on models

[Xipooo]

I have an actor model based around the MySQL sakila demo database. There are no CreatedAt or UpdatedAt fields in either the table or model. Yet when I create an initial migration this tool automatically adds them which causes the server to throw an "Unhandled rejection SequelizeDatabaseError: Unknown column 'createdAt' in 'field list'" error when sync'd.

I know how to get around this error by disabling timestamps in my server configuration, but the behavior is quite annoying. The migration shouldn't be adding columns to models that don't exist either in the model definition nor the original database.

[Iwuaa]

same issue here

[billkiddo]

I know how to get around this error by disabling timestamps in my server configuration

@Xipooo can you offer more details on how you did it? how the config looks like?