hasura / hasura/graphql-engine
Migration script unable to drop table
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Problem: I recently updated the Hasura version from v1.3.4-beta.3 to v2.0.9 and received the following error:
```
description: "view schema_update depends on table hdb_catalog.hdb_schema_update_event"
exec_status: "FatalError"
hint: "Use DROP ... CASCADE to drop the dependent objects too."
```
But the migration script was not able to drop table hdb_catalog.hdb_schema_update_event. In lieu of that, I had to drop `view public.schema_update`.
So now the question is: Do we need this view still in the new version? e.g
```
CREATE OR REPLACE VIEW public.schema_update
AS SELECT hdb_schema_update_event.occurred_at
FROM hdb_catalog.hdb_schema_update_event;
```
Contributor guide
Research direction
Start by reviewing the migration from Hasura v1.3.4-beta.3 to v2.0.9 and the dependency between public.schema_update and hdb_catalog.hdb_schema_update_event. Determine whether the view is still required and whether the migration can drop the table without manual intervention; the migration should complete successfully with the intended schema objects intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100