-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
--dump-schema
does not dump media handlers
#3237
Comments
This seems to be the case ever since 82b3834 introduced this line of code: , "dbMediaHandlers" .= JSON.emptyArray We have the same for timezones: Why? |
Those were left out of the schema dump when the features were introduced, probably because ByteString doesn't have a toJSON instance. Changing the type to Text solves this easily. Resolves PostgREST#3237
Ah, my bad. I forgot to mark that as TODO. It should be filled.
I recall this one was on purpose, to not expose it via OpenAPI. But on second thought, would it makes sense to expose it? I guess we could list all |
This is only about dumping the schema cache, not about openapi. #3238 dumps it now, too - but that doesn't mean it needs to go anywhere else, right? |
Those were left out of the schema dump when the features were introduced, probably because ByteString doesn't have a toJSON instance. Changing the type to Text solves this easily. Resolves PostgREST#3237
Those were left out of the schema dump when the features were introduced, probably because ByteString doesn't have a toJSON instance. Changing the type to Text solves this easily. Resolves PostgREST#3237
Those were left out of the schema dump when the features were introduced, probably because ByteString doesn't have a toJSON instance. Changing the type to Text solves this easily. Resolves #3237
Environment
Description of issue
While trying to debug another possible regression in the current development version, I wanted to see the media handlers via
--dump-schema
.(Edit: The following commands only work after 4a796e0)
Running
postgrest-with-postgresql-16 -f test/spec/fixtures/load.sql postgrest-run
responds with:Nice!
But,
postgrest-with-postgresql-16 -f test/spec/fixtures/load.sql postgrest-run --dump-schema | jq '.dbMediaHandlers'
then gives me:Something is broken there.
In fact, counting the array items of the json response:
Not sure if timezones is broken as well?
The text was updated successfully, but these errors were encountered: