Drizzle 0.30.4 Missed Six PostgreSQL Parent Tables and Stalled the CI Pipeline

A recent deployment pipeline failed at the migration stage, revealing an issue with the 0.30.4 version of the Drizzle ORM. The migration script attempted to reconcile the database schema using the `drizzle-kit push` command but became stuck in an interactive menu, unable to submit a response. This occurred because the command fed an endless stream of input that the menu did not recognize as a valid submission.

The migration process consisted of two phases: the first created the ORM schema, while the second applied SQL files to every deployment. However, the script did not maintain any migration history. The PostgreSQL database, on the other hand, did not show any active queries or idle sessions during the investigation. The log tail suggested the client was waiting for keyboard input, but the input was not being recognized by the menu.

The menu displayed a prompt asking whether a parent table was created or renamed, but the script could not submit a valid response due to the non-interactive nature of the input stream.

The database contained six partitioned parent tables, each with 96 children. The migration script incorrectly reported only the 96 children as tables while omitting the six parents. The ORM schema declared the six parents, leading the migration process to ask for a rename for each missing parent, including the partitioned children.

The script defaulted to creating a parent table, which failed because the parent table already existed in PostgreSQL but was not visible to the introspection query. This issue highlights the limitations of the `drizzle-kit push` command in handling non-interactive migrations and the importance of properly documenting expected user inputs for safety controls.