drizzle-kit introspect creating schema views with pgTable

[hardysabs2]

When I run drizzle-kit introspect the tables and views in my PostgreSQL database are both being created in schema.ts using pgTable.

I have amongst others
table - "company"
view - "Company"

The schema.ts has generated to it

export const company = pgTable("company", {...})

and

export const company = pgTable("Company", {...})

This has eslint errors and so will not compile.

I presume there may be some config I am missing. I am on

"drizzle-kit": "^0.24.2",
"drizzle-orm": "^0.33.0",

Any advice appreciated.

[AlexDaniel]

Just replace pgTable with pgView. Drizzle kit is confused by views and creates them as if they were tables. Materialized views are ignored altogether and need to be done by hand. I believe this will be resolved eventually as materialized views are on the roadmap.

[hardysabs2]

I understood one of the key points with drizzle was that one could take what features you wanted and leave others. My plan is to just use the SQL like query builder with type safety. This means periodically running introspect after underlying database changes.

I am migrating schema and data from MS SQL Server to PostgreSQL and the views in PostgreSQL are to allow us to make a gradual code changes to switch to PostgreSQL naming convention, not all at once. Therefore there is one view for every table and the table and view names are similar in PostgreSQL, e.g. Company & company or CompanyAccount & company_account, but the const is usually identical so the schema.ts will not compile until I at least edit one of every const pair but as you say also change half the pgTable to pgView.

This is going to be pretty inconvenient. You mention a fix for Materialized views but is there any plan to fix it not recognising views generally?

One thing that comes to mind is a simple renaming of the new pg tables, perhaps each ending in _t, then the schema consts would be different and the ts would compile. The only thing remaining would be that the views would be created in schema.ts with pgTable not pgView. So far I have not seen any consequences from this.

Will there be any?