Khalil Sarwari

## GORM Playground Link https://github.com/go-gorm/playground/pull/496 ## Description Once a generated column is created in postgres, it cannot be altered so it should be skipped during automigration. This is also discussed...

Follow up to #43 but for batch scenario

potential type mismatch in eval mode?

1

1.) vision_transformer `forward` does `self.head(ret["x_norm_clstoken"])` in eval, where `ret` is the result of `forward_features` https://github.com/facebookresearch/dinov2/blob/ea5276ec8c27d7db59632cf75870cb3c1037de1f/dinov2/models/vision_transformer.py#L290 2.) the value of `forward_features` can be the result of `forward_features_list` https://github.com/facebookresearch/dinov2/blob/ea5276ec8c27d7db59632cf75870cb3c1037de1f/dinov2/models/vision_transformer.py#L223 3.) `forward_features_list` returns...

Once a generated column is created in postgres, it cannot be altered so it should be skipped during automigration. This is also discussed [here](https://github.com/go-gorm/gorm/issues/4946), there is a really solid breakdown...