# Table does not exist in the current database

**URL:** <https://community.fly.io/t/table-does-not-exist-in-the-current-database/4325>\
**Category:** Questions / Help\
**Tags:** postgres\
**Created:** [March 9, 2022, 5:40pm UTC](https://community.fly.io/t/table-does-not-exist-in-the-current-database/4325 "2022-03-09T17:40:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![binajmen](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/binajmen/32/13396_2.png) [@binajmen](https://community.fly.io/u/binajmen)\
**Post date:** [March 9, 2022, 5:40pm UTC](https://community.fly.io/t/table-does-not-exist-in-the-current-database/4325/1 "2022-03-09T17:40:43Z")

</div>

Hi.

I deployed an app I’m currently developing, just to try [fly.io](http://fly.io). I’ve created a proxy to the fly db to perform a nasty `npx prisma db push` . Sure it is not conventional, but this is a dev environment, don’t judge me 😉

However, I have the following prisma error:

```auto
Invalid `prisma.group.findUnique()` invocation: The table `public.Group` does not exist in the current database.

```

Using `flyctl postgres connect` , I list the tables and test a selection on the Group table, with no success… But the table is listed.

```auto
# \dt
                List of relations
 Schema | Name | Type | Owner   
--------+---------------------+-------+----------
 public | Group | table | postgres
 ...
(19 rows)

# select * from Group;
ERROR: syntax error at or near "Group"
LINE 1: select * from Group;
                      ^

```

When I create a proxy (`flyctl proxy` …) to connect with pgAdmin, I can access the tables (and the content) in the public schema of my app db.

What could I do wrong?

---

<div class="post-metadata">

**Author:** ![binajmen](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/binajmen/32/13396_2.png) [@binajmen](https://community.fly.io/u/binajmen)\
**Post date:** [March 9, 2022, 7:43pm UTC](https://community.fly.io/t/table-does-not-exist-in-the-current-database/4325/2 "2022-03-09T19:43:03Z")

</div>

Ok not sure what happened but it seems unsetting/setting the secrets did solved the problem. Can’t say if the old secret was incorrect, although the old DIGEST and the new DIGEST are different (but I don’t know how this value is computed).