Bug fixes
Big thanks to @L-Mario564 for his PR. It conflicted in most cases with a PR that was merged, but we incorporated some of his logic. Merging it would have caused more problems and taken more time to resolve, so we just took a few things from his PR, like removing "::" mappings in introspect and some array type default handlers
What was fixed
- The Drizzle Kit CLI was not working properly for the
introspectcommand. - Added the ability to use column names with special characters for all dialects.
- Included PostgreSQL sequences in the introspection process.
- Reworked array type introspection and added all test cases.
- Fixed all (we hope) default issues in PostgreSQL, where
::<type>was included in the introspected output. preservecasing option was broken
Tickets that were closed
- [BUG]: invalid schema generation with drizzle-kit introspect:pg
- [BUG][mysql introspection]: TS error when introspect column including colon
- [BUG]: Unhandled defaults when introspecting postgres db
- [BUG]: PostgreSQL Enum Naming and Schema Typing Issue
- [BUG]: drizzle-kit instrospect command generates syntax error on varchar column types
- [BUG]: Introspecting varchar[] type produces syntactically invalid schema.ts
- [BUG]: introspect:pg column not using generated enum name
- [BUG]: drizzle-kit introspect casing "preserve" config not working
- [BUG]: drizzle-kit introspect fails on required param that is defined
- [BUG]: Error when running npx drizzle-kit introspect: "Expected object, received string"
- [BUG]: Missing index names when running introspect command [MYSQL]
- [BUG]: drizzle-kit introspect TypeError: Cannot read properties of undefined (reading 'toLowerCase')
- [BUG]: Wrong column name when using PgEnum.array()
- [BUG]: Incorrect Schema Generated when introspecting extisting pg database
- [⚠️🐞BUG]: index() missing argument after introspection, causes tsc error that fails the build
- [BUG]: drizzle-kit introspect small errors
- [BUG]: Missing bigint import in drizzle-kit introspect