Unsupported column type DATE

[swiss-knight]

Description
When using a PostgreSQL table, starting pygeoapi from its official docker image leads to this message:
pygeoapi-1 | Unsupported column type DATE

which may be related to a column of type DATE in my PostgreSQL database.

Steps to Reproduce
Set up a provider to link a PostgreSQL table having a DATE column

Expected behavior
is that pygeoapi doesn't raises such message with PostgreSQL DATE type.

Screenshots/Tracebacks

$ docker compose up -d && docker compose logs -tf pygeoapi
[+] up 2/2
 ✔ Container my-app-db-1       Healthy                                                                                                                                                               0.5s
 ✔ Container my-app-pygeoapi-1 Running                                                                                                                                                               0.0s
pygeoapi-1  | START /entrypoint.sh
pygeoapi-1  | Default config in /pygeoapi/local.config.yml
pygeoapi-1  | Trying to generate openapi.yml
pygeoapi-1  | Unsupported column type DATE  # <----------------- here's the message
pygeoapi-1  | Generating /pygeoapi/local.openapi.yml
pygeoapi-1  | Done
pygeoapi-1  | openapi.yml generated continue to pygeoapi
pygeoapi-1  | Trying to generate asyncapi.yml
pygeoapi-1  | pubsub not configured; aborting
pygeoapi-1  | asyncapi.yml could not be generated; skipping
pygeoapi-1  | make SCRIPT_NAME empty from /
pygeoapi-1  | Starting gunicorn name=pygeoapi on 0.0.0.0:80 with 4 workers and SCRIPT_NAME=
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [1] [INFO] Starting gunicorn 23.0.0
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1)
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [1] [INFO] Using worker: gevent
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [9] [INFO] Booting worker with pid: 9
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [10] [INFO] Booting worker with pid: 10
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [11] [INFO] Booting worker with pid: 11
pygeoapi-1  | [2026-03-09 13:15:42 +0000] [12] [INFO] Booting worker with pid: 12
pygeoapi-1  | AsyncAPI document /pygeoapi/local.asyncapi.yml does not exist.  Please generate before starting pygeoapi
pygeoapi-1  | AsyncAPI document /pygeoapi/local.asyncapi.yml does not exist.  Please generate before starting pygeoapi
pygeoapi-1  | AsyncAPI document /pygeoapi/local.asyncapi.yml does not exist.  Please generate before starting pygeoapi
pygeoapi-1  | AsyncAPI document /pygeoapi/local.asyncapi.yml does not exist.  Please generate before starting pygeoapi

Environment

• OS: based on docker image geopython/pygeoapi:latest
• Python version: based on docker image geopython/pygeoapi:latest
• pygeoapi version: based on docker image geopython/pygeoapi:latest

[tomkralidis]

@swiss-knight I'm unable to reproduce against the following schema:

test=# \d roads 
                                          Table "public.roads"
   Column   |           Type            | Collation | Nullable |                Default                 
------------+---------------------------+-----------+----------+----------------------------------------
 road_id    | integer                   |           | not null | nextval('roads_road_id_seq'::regclass)
 road_name  | character varying(64)     |           |          | 
 date_added | date                      |           |          | 
 geom       | geometry(LineString,4326) |           |          | 
Indexes:
    "roads_pkey" PRIMARY KEY, btree (road_id)

test=# 

Can you post a sample table schema as well as minimal provider configuration?