Graphql-engine: allow db-reset

[wawhal]

Either the server or the CLI should allow users to reset their database.

[shahidhk]

I don't think we should do this since we are not managing postgres.

Let's re-open if someone shows interest.

[snarlynarwhal]

I concur, I would like this functionality also.

[coco98]

Atleast we can document this right?

Drop schema public cascade;
Drop schema hdb_views cascade;
Drop schema hdb_catalog cascade;
Create schema public;

First and last lines are optional.

On Tue, 20 Nov 2018 at 6:56 AM, PJ Legendre [e-mail]
wrote:

I concur, I would like this functionality also.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hasura/graphql-engine/issues/289#issuecomment-440301882,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIAWLg497Ak1zTisveOO9JiQSSbyenyks5uxBg6gaJpZM4V_T7v
.

[snarlynarwhal]

Ahhh thank you so much!

[miqvo]

@coco98 did this change in beta 6? I get unexpected : relation "hdb_catalog.hdb_column" does not exist when trying to drop the hdb_catalog schema.

[afreix]

@miqvo I ran into a similar problem. I just deleted everything from my database and then re-ran an instance of hasura, which re-populated the necessary tables within the hdb_catalog schema

[mnlbox]

@shahidhk Please reopen this issue for more better ducumentation.

[pnappa]

@coco98 did this change in beta 6? I get unexpected : relation "hdb_catalog.hdb_column" does not exist when trying to drop the hdb_catalog schema.

I had to scroll back in the Discord for info about this one - you don't do it in the Run SQL page in Hasura, you need to do it directly on the database, i.e. run psql and connect to it. Doing it that way worked for me!