snapshot of https://github.com/ent/ent.git (master, 2026-09-15; blobs > 131072B omitted)
Some checks failed
Atlas CI Public / lint (push) Failing after 13s
Atlas CI Public / sync (push) Has been skipped

This commit is contained in:
upstream-mirror
2026-09-15 22:12:36 +05:00
commit 4b3ad0b611
2680 changed files with 719472 additions and 0 deletions

View File

@@ -0,0 +1,14 @@
## Define PostgreSQL Views in Ent Schema
This example demonstrates how to define an `ent.View` with its SQL definition (`AS ...`) specified in the Ent schema.
The second approach is to define an `ent.View` but keep its definition and creation externally using the Atlas `composite_schema`
data source (see `examples/viewcomposite` for more information).
The main advantage of this example approach is that the `CREATE VIEW` correctness is checked during migration and not during queries.
For example, if one of the `ent.Field`s defined in your ent/schema does not exist in your SQL definition, PostgreSQL will return the
following error:
```text
create "clean_users" view: pq: CREATE VIEW specifies more column names than columns
```