Introspection: Warn about database construct that PSL can not express

[janpio]

When introspecting, Prisma currently only looks at the things it understands and can express via Prisma Schema Language in a Prisma Schema. When migrating the database later, the user has to ensure manually that all not understood features are added to migrations manually.

(Exceptions: Unsupported field types are introspected and expressed with Unsupported("...") and native database functions in defaults via dbgenerated("...") - and Migrations will use the raw string inside the function and use that in the generated SQL. Unsupported field types can then queried via Prisma's raw sql functions, and native database functions will be used by the database itself.)

Examples of constructs Prisma can currently not express in PSL, and hence skips during Introspection are:

• Indexes and Constraints:
  • Gin/Gist index operator classes brought in via PostgreSQL extensions
  • Conditional unique constraints + Partial indexes
  • Expression indexes
  • Index INCLUDE clause
  • Check constraints
  • Deferred constraints
  • Index sort order, NULL behavior
  • Full Text Indexes in PostgreSQL and SQL Server
  • TTL indexes in MongoDB
  • PostgreSQL btree_gin based indexes
  • Sparse Unique indexes in MongoDB
  • PostgreSQL Exclusion Constraints
• Stored procedures
• Triggers
• Unsigned integers
• Collations in MySQL and MongoDB
• PostgreSQL Row Level Security Policies
• PostgreSQL generated columns
• Table Partitioning
• User-defined types
• Table and field comments
• PostgreSQL DOMAIN
• Multi dimensional arrays
• Nullable lists
• Multiple foreign keys on the same column
• Relations on lists
• IDENTITY columns in PostgreSQL
• PostgreSQL Foreign Data Wrappers
• CockroachDB row-level TTL
• Temporal data
• $jsonSchema for MongoDB
• MongoDB time series collections
• MySQL scheduled events
• SQLite STRICT tables
• User/Grants management

Instead of just ignoring and skipping these, Prisma could detect them and output a warning after Introspection that this construct did not find its was into the Prisma Schema, and hence has to be handled manually.