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
Describe the bug supabase db diff is not completing successfully, and cannot see the geography type which is a postgis plugin type.
I've verified that both my remote and local databases have the type registered as \dT geography will return:
postgres=> \dT geography
List of data types
Schema | Name | Description
------------+-----------+------------------------------------------------------------------------------------------------------
extensions | geography | postgis type: The type representing spatial features with geodetic (ellipsoidal) coordinate systems.
(1 row)
I have a few different schemas outside of public, and I'm wondering if this is causing the issue specifically. I have a schema called hydrology which has a table called access_point and uses a geography datatype column.
To Reproduce
Steps to reproduce the behavior:
Create a new schema
Use the postgis extension
Create a column that uses the geography datatype
Run supabase db diff
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with --create-ticket flag.
Describe the bug
supabase db diff
is not completing successfully, and cannot see the geography type which is a postgis plugin type.I've verified that both my remote and local databases have the type registered as
\dT geography
will return:I have a few different schemas outside of public, and I'm wondering if this is causing the issue specifically. I have a schema called
hydrology
which has a table calledaccess_point
and uses ageography
datatype column.To Reproduce
Steps to reproduce the behavior:
supabase db diff
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with
--create-ticket
flag.─────────────────────────┼──────────────────────┼────────────
supabase/postgres │ 15.1.1.78 │ 15.1.1.78
supabase/gotrue │ v2.156.0 │ v2.158.1
postgrest/postgrest │ v12.2.2 │ v12.2.2
supabase/realtime │ v2.28.32 │ -
supabase/storage-api │ v1.6.8 │ v1.6.8
supabase/edge-runtime │ v1.45.2 │ -
supabase/studio │ 20240422-5cf8f30 │ -
supabase/postgres-meta │ v0.80.0 │ -
supabase/logflare │ 1.4.0 │ -
bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ -
darthsim/imgproxy │ v3.8.0 │ -
The text was updated successfully, but these errors were encountered: