What about migrations?

I stumbled on your post while researching how to use postgres views with diesel. I had seen this workaround before but this articled helped solidify some things I was thinking about.

What it does not mention though is that if you manager your schema with migrations, Diesel will leave you in the cold, because it only prints-schemas with tables and such... Views will go missing every time diesel regenerates your schema file.

A way to fix that is to use the patch_file config in the diesel.toml... If you create a patch file from the diff of your view in the schema.rs file, it will apply the patch AFTER it generates the schema and you have your views remaining in the schema.rs.

Hopefully this helps someone

The issue describes a Diesel migration and schema-generation workaround but names no documentation file, test, or concrete change. Start by locating the referenced post and its source, then determine where migration-related guidance belongs. Done would require an agreed documentation target and clear coverage of the reported views behavior.

Written by the indexing model from the issue text.