Allow Postgres adapter's beforeSchemaInit to handle sql views

[JesperWe]

Describe the Bug

The docs state about beforeSchemaInit:

Runs before the schema is built. You can use this hook to extend your database structure with tables that won't be managed by Payload. ... One use case is preserving your existing database structure when migrating to Payload.

The ability to perserve existing database structure is however limited to databases that have tables that are not to be managed by Payload.
If the DB has SQL views defiend, Drizzle will attempt to delete those views and there is no way in the PostgresSchema type to add views, it only supports Enums, Relations and Tables.

Drizzle itself supports adding pgView, but that feature does not seem to be propagated.

Link to the code that reproduces this issue

https://github.com/payloadcms/payload/blob/beta/packages/drizzle/src/postgres/types.ts

Reproduction Steps

One easy way to reproduce is to enable the very popular PostGIS extension in a Postgres database

CREATE EXTENSION postgis;

and then try to enable Payload for that database. The extra spatial_ref_sys table required by PostGIS can be handled in beforeSchemaInit but the required views can not. Drizzle will try to delete them, which will fail.

Which area(s) are affected? (Select all that apply)

db-postgres

Environment Info

Binaries:
Node: 20.11.0
npm: 10.8.2
Yarn: 1.22.19
pnpm: 9.12.2
Relevant Packages:
payload: 3.0.0-beta.123
next: 15.0.1
@payloadcms/db-mongodb: 3.0.0-beta.123
@payloadcms/db-postgres: 3.0.0-beta.123
@payloadcms/graphql: 3.0.0-beta.123
@payloadcms/next/utilities: 3.0.0-beta.123
@payloadcms/richtext-lexical: 3.0.0-beta.123
@payloadcms/richtext-slate: 3.0.0-beta.123
@payloadcms/translations: 3.0.0-beta.123
@payloadcms/ui/shared: 3.0.0-beta.123
react: 19.0.0-rc-65a56d0e-20241020
react-dom: 19.0.0-rc-65a56d0e-20241020

[jmikrut]

Hey @JesperWe — I think this is something that we can likely add to Payload. Good call. I will add this to the roadmap and we should be able to get to it shortly!

[max-degterev]

Yep and integrated support for GIS would be awesome

[JesperWe]

Yep and integrated support for GIS would be awesome

Yes it would, but it is something that would not be too hard to implement yourself with all the flexibility of Custom Components that Payload has.

This issue does make it way harder, since adding the PostGIS extension to a DB breaks Payload in a deep Drizzle way that is not that easy to work around.

For now I work around it by storing GeoJSON in a Payload JSON field. But without PostGIS you loose all ability to do stuff like sorting based on distance etc.

So thanks for making it a prio roadmap thing!

[max-degterev]

With first party GIS we get polygon/polyline which is essential for routing

[stefgootzen]

Also big +1 for this. We solve it by storing our geometries in a completely different database. That obviously doesn't allow you to use joins/relationships/fk's to payload's managed database.

[r1tsuu]

Update here. PostGIS / Point field support will be very soon, check the comment from @ainsleyclark #8644 (comment) in the related discussion for this!

As soon as Drizzle's PR will be released I think we can also merge this.