You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to allow the model to have missing (undeclared) fields (columns) when .Column("*") is used?
Example:
db.NewSelect().Model(&user).Column("*")
This throws an error if the users table has a column that is not defined in the User model. I need a smaller model that does not include every column in the table.
I know that I can define each column I need in the .Column("col1", "col2") but I wish that I don't have to write the entire model manually.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. If there is no update within the next 7 days, this issue will be closed.
Is there any way to allow the model to have missing (undeclared) fields (columns) when
.Column("*")
is used?Example:
This throws an error if the
users
table has a column that is not defined in theUser
model. I need a smaller model that does not include every column in the table.I know that I can define each column I need in the
.Column("col1", "col2")
but I wish that I don't have to write the entire model manually.The text was updated successfully, but these errors were encountered: