I already tried that and that works, I get:

id | done | task | due
----+------+-------------------+-----
1 | f | finish tutorial 0 |
2 | f | pat self on back |
(2 rows)

although it's not likely, try restarting postgrest.

after that please post a copy/paste of the entire console session for the following commands

• cat postgrest.conf
• psql
  • select * from api.todos;

Restarting didn't help.

I'm using c9, so I can't access postgrest.conf

But here is:

ubuntu=# select * from api.todos;
 id | done |       task        | due 
----+------+-------------------+-----
  1 | f    | finish tutorial 0 | 
  2 | f    | pat self on back  | 
(2 rows)

this does not help, the point was to compare the connection string you put in postgrest.conf with the way to connect directly to the db and make sure you are not mixing things. the result of th query is irelevant

I read "postgres.conf" thought it was something related to postgresql not postgrest.

I have a tutorial.conf file:

db-uri = "postgres://postgres:mysecretpassword@localhost/postgres"
db-schema = "api"
db-anon-role = "web_anon"

ok, so here is what i don't get.
you say you are using c9 (which i am not familiar with) then you paste your conf file which references the localhost.
If you are running postgrest in c9 that means localhost is that remote computer, not your computer, while you are probably using using psql with the same connection string and that gets you connected to the postgre instance on your actual computer, not the db where postgrest running in c9 is connecting.
Tutorial was written with the idea that you are doing everything on your actual computer. If you start mixing different remote environments then you are on your own :) to figure out what is going wrong.

(to reiterate, IMO this is what's happening, postgrest is connecting to the database that is on the same host where it is running, i.e. c9, while you executed the sql from the tutorial using psql on your computer and not the db where postgrest is connecting)

did you figure it out? was ti the c9 thing?

@amadeuspagel did you make any progress with this?

Ran into the same issue - resolved by turning off PostgresApp... Postgrest was connecting to my local Postgres rather than Docker - cheers!

Closing due to lack of activiy, reopen if problem persists.

Hi,

I've the same issue here.
I tought it was because my tables were not in lower case. So I tried a dummy test and create a db and 1 table in lower case : same issue.

Running x64 windows version. Pg is in version 10.0
HTTP command : GET http://localhost:3000/flattable
db name : pgwebtest
mytest.conf:
db-uri = "postgres://postgres:postgres@localhost:5432/"
db-schema = "pgwebtest"
db-anon-role = "web_anon"

webservice answer:
HTTP/1.1 404 Not Found
Transfer-Encoding: chunked
Date: Fri, 08 Feb 2019 03:21:03 GMT
Server: postgrest/5.2.0 (1e732ac)
Content-Type: application/json; charset=utf-8

{"hint":null,"details":null,"code":"42P01","message":"relation "pgwebtest.flattable" does not exist"}

PostgREST connects successfully. My table is in the public schema of my db.

Any idea ?

@CygaLV Should be db-uri = "postgres://postgres:postgres@localhost:5432/pgwebtest" and db-schema="public"

hi, I got same issue, here is some info

1. db logs:

2019-02-16 17:21:59.918 UTC [1] LOG:  database system is ready to accept connections
2019-02-16 17:22:01.717 UTC [29] ERROR:  relation "fling.user_base" does not exist at character 61
2019-02-16 17:22:01.717 UTC [29] STATEMENT:  
            WITH pg_source AS (SELECT "fling"."user_base".* FROM "fling"."user_base"    ) SELECT null AS total_result_set, pg_catalog.count(_postgrest_t) AS page_total, array[]::text[] AS header, coalesce(json_agg(_postgrest_t), '[]')::character varying AS body
            FROM ( SELECT * FROM pg_source) _postgrest_t 

2. I search with same schema in db is ok

postgres=# SELECT "fling"."user_base".* FROM "fling"."user_base";
 avatar | create_time | gender | id | location | marital_status | name | password | update_time 
--------+-------------+--------+----+----------+----------------+------+----------+-------------
(0 rows)

3. some of my docker-compose.yml

  api:
    image: postgrest/postgrest
    environment:
      PGRST_DB_URI: postgres://postgres:password@db:5432/fling
      PGRST_DB_SCHEMA: fling
      PGRST_DB_ANON_ROLE: web_anon
  db:
    image: postgres
    environment:
      POSTGRES_DB: fling
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: password

I just fllow the tutorial, no more change for config. help me pls!

The postgrest docker container is probably connecting to your local db(on 5432 port). Specify the ports of your db in docker-compose(on port 5433 maybe) and connect postgrest to that instance.

I solved the problem.
In my case, it was because I had created the schema and the table in another database than the default one (postgres). If you do so, don't forget to change the name of the database at the end of the URL : db-uri = "postgres://authenticator:mysecretpassword@localhost:5433/YOUR-DATABASE-NAME"