Marius A

> Can we give v3 support on 4.1? That's a good plan. > and close this issue? After it's done :)

I made the change, but it still doesn't read from db. Quoting from https://sequelize.org/master/class/lib/data-types.js~VIRTUAL.html ``` If a virtual attribute is present in attributes it will automatically pull in the extra...

How about introducing a new property, `readOnly: true` ? Shall I enter this request in https://github.com/sequelize/sequelize ?

That won't work either (on UPDATE it will set values), and it's confusing. But I found it would be ~easy to add, similar to `autoIncrement`, so thanks for the suggestion...

Here's a workaround: https://stackoverflow.com/questions/67051281/use-postgres-generated-columns-in-sequelize-model/67120448#67120448 Would it be possible to implement this in sequelize-auto, until proper readOnly support comes to sequelize?

PS: the default value is already set in db. It would make sense to leave out that JSONB column on insert, if not specifically set in `.create()`. Changing default column...

Just tested deleting `defaultValue` and everything works great. The best solution for this issue would be #592

see https://github.com/sequelize/sequelize-auto/issues/592 for a proposed solution

@steveschmitt What do you think? Now, every time we re-generate models we need to remove default values for everything to work properly.

README's usage instructions doesn't work, I get same error as in #91 ``` Uncaught (in promise): TypeError: fs.readFileSync is not a function(…) in input.js ``` @itsalb3rt comment does work, thanks!