You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating first list on fresh install, receive GraphQL error in admin dashboard
When trying to add my first list on a fresh install using Postgres and the users/auth starter I receive a GraphQL error when logging into admin
GraphQL error: select count(*) from "public"."Clinic" as "t0" where true - relation "public.Clinic" does not exist
GraphQL error: select "t0".* from "public"."Clinic" as "t0" where true order by "name" ASC limit $1 - relation "public.Clinic" does not exist GraphQL error: select count(*) from "public"."Clinic" as "t0" where true and "t0"."name" ~* $1 - relation "public.Clinic" does not exist
To Reproduce
Install with yarn create keystone-app app-name
Choose users/auth starter
Choose Postgres and postgres connection string (connects ok)
It's likely you need to run yarn create-tables. For the Knex Adapter Keystone will not automatically initialise an SQL database, but there is a command to do this.
Clarifying @MadeByMike's comment -- the yarn create-tables command creates tables in your DB for the lists currently defined in your Keystone schema. Based on your reproduction steps, it looks like you may have run yarn create-tables (step 4) then added the list to your schema (step 5). Just reverse these two steps!
Hi @molomby thanks so much for your reply, I will go back to my project and try it this way around, it's possible I hadn't got it the right way around!
When creating first list on fresh install, receive GraphQL error in admin dashboard
When trying to add my first list on a fresh install using Postgres and the users/auth starter I receive a GraphQL error when logging into admin
To Reproduce
yarn create keystone-app app-name
yarn create-tables
Clinic
list:Expected behaviour
Expected to be able to access this new model in the admin
System information
The text was updated successfully, but these errors were encountered: