-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to customise mutableColumns to read-only generated columns in PostgreSQL? #209
Comments
Hi @rangzen, Currently it is not possible to exclude columns from var PeopleAllColumns = People.AllColumns.Except(People.HeightIn)
var PeopleMutableColumns = People.MutableColumns.Except(People.HeightIn) In terms of implementation, I suppose adding a new `Skip' flag would be enough to signal that the column should not appear in table sql builder struct. |
I just want to clarify that Postgres generated columns are read only. The goal would be to keep them in |
Aha, I see. In that case implementation can be simplified. We can retrieve additional column The only concern is this might affect existing users. But I think it should be fine, because generated columns can't be used in either insert or update statements, so existing users are probably already excluding generated columns. |
@go-jet PR and data pushed. Not sure how you deal with the submodule. |
Yep, CircleCI need first the link to the data submodule |
Yeah, when |
Hello,
We use generated columns with PostgreSQL, see Generated Columns.
We would like to exclude these columns from the generated mutableColumns list.
Can we use something like Generator customization?
Is this possible without adding fields to
metadata.Table
ormetadata.Column
? Without changingDefaultTableModel(tableMetaData metadata.Table) TableModel
to an interface to reimplement(t table) MutableColumns() []Column
?Thank you!
The text was updated successfully, but these errors were encountered: