sql: fix statement bundle recreate with non-default schema #91099
Labels
C-cleanup
Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
E-quick-win
Likely to be a quick win for someone experienced.
T-sql-queries
SQL Queries Team
Currently, if a statement bundle is collected while using a non-default db, we won't be able to recreate it via
debug statement-bundle recreate
without manually modifying the schema (and possibly the statement). This is the case because we put fully-qualified table names intoschema.sql
, yet we don't recreate the database nor the schema of those objects. We could either teach the recreate command to handle such errors, or (which is better) include the SQL statements to create the necessary objects intoschema.sql
right away.Jira issue: CRDB-21105
The text was updated successfully, but these errors were encountered: