Steve Schmitt

You could try adding `autoIncrement: true` to your field definition. I think that will tell sequelize to read but not write the field.

Yes, I think if the type definition has "GENERATED" or "STORED", then we could add a `set()` method that throws an Error.

Hmm, I wonder what changed. Can you provide a CREATE TABLE script that I can use to test?

Thanks for finding this. Do you have an idea for the fix? What should the sequelize-auto output be for your model? One work around is to use the model name...

Yes, with a unique constraint on `bars.foo_id`, each `foo` can only have one `bar`. It seems the constraint checking in sequelize-auto is not correct.

Yes, that make sense. We need to review the way that imports are written.

I tried changing them, but it didn't seem to work.

No plans. It's quite a different model from sequelize-auto does.

I'm not sure that I understand the problem. The `init-models` creates a relationship, and you are creating the same relationship? Or you are creating a different relationship, but you want...

Hmm. Sounds like a sequelize bug. Does it work if both `belongsToMany` relationships specify an "as" that is not the table name?