The search functionality in the Data & Schema Management of Hasura seems to filter records considering the case of letters as well.
If this was an intended functionality, it's still better to show the tables which match the filter condition and don't match the letter-case below the tables that match with the exact letter-case.

Environment

• PostgreSQL version: All
• PostgREST+ version: 6.0.2 (713b214)

Current state

Currently, Comment on Table

COMMENT ON SCHEMA todos IS
  'Todos object description';

generate a summary for all operations on this resource

 /todos:
    get:
      tags:
        - todos
      summary: Todos object description
      parameters:

But sum

I'm submitting a ...

• bug report
• [ X] feature request
• question

PostGraphile version: 4.4.4

postgraphile should honor variables in query string as defined in https://github.com/graphql/express-graphql#http-usage when the query is provided as post body.

with the following exampl

I think the plugins docs need to extend beyond a single page now. I want to add a whole section on writing tests for plugins, showing how httpx can be used as seen in simonw/datasette-atom#3 and suchlike.

As of first congrats for this package - I'm using it quite often & it's a great help.

I'd like to ask a feature request - add support for MSSQL DB.
The main official mode of connection recommended by MS is ODBC/PDO.
[https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-2017#microsoft-odbc-driver-17-for-sql-server](ht

• pREST version (or commit ref): 3.4
• pREST endpoint: /DB0001/public/test?Auto%20ID=25
• PostgreSQL version: 10.6
• Operating system: Linux
• Go version: bundled in release
• Log gist: https://gist.github.com/baybal/c6059538121443aaad2dddf17108aead

Description

Attempting to filter of select a field with a white space results in invalid identifier error

`{
"error": "could not pe

Thanks for making such great code. I've got an instance running and am trying to document the ways that I can query the API.

So far, I've found:

• ?page=2
• ?[columnheader]=[value]
• ?[columnheader1]=[value1]&[columnheader3]=[value4] (returns results that have both value1 and value2)
• ?[columnheader1]=[value1]&[columnheader1]=[value2] (returns results that have value1 OR value2)

I'

Since MySQL is removed from the opensource version in version 3.0, and all users are stored in MySQL as the default storage, I guess we will have to migrate that to SQLite that is the new default storage for config and DF users. But there are no documentation at all about upgrading from 2.x -> 3.x, nor any release notes in the Wiki for 3.x.

Are there more breaking changes or things to consider

What would you like to be added:

Document what it would take to get Super Graph working with Yugabyte DB a distributed database that is designed to be compatible with Postgres. Super Graph makes use of a bunch of Postgres specific features like querying for database tables and columns, lateral joins, json functions et