So, i just install ReadySet at my local with my Postgres 14 existing.

Then, i just want to select my "Table" with specific type like enum or geography. When i try to query got this error.

ERROR:  internal error: could not retrieve expected column index 3 from row while parsing psql result: error deserializing column 3: cannot convert between the Rust type `noria_data::DataType` and the Postgres type `geography`

this is bug? or i just wrong install

btw, great work for doing this. Keep it up.

Similar to #6:

Any query through Readyset that attempts to select a character varying(n)[] column seems to result in the following type of error:

ERROR:  internal error: could not retrieve expected column index 1 from row while parsing psql result: error deserializing column 1: cannot convert between the Rust type `noria_data::DataType` and the Postgres type `_varchar`

Ie, for a table that looks like:

CREATE TABLE some_table (
    id uuid DEFAULT uuid_generate_v4() PRIMARY KEY,
    some_text_array character varying(5)[],
);

select id, some_text_array from some_table -- query will result in the above error

select id from some_table -- query will succeed

Is your feature request related to a problem? Please describe. See a potential to have a feature to move 3rd party data integrations closer to the DB. For example, based on some condition or CRUD operations on any db table - to be able to post data to 3rd party end-points via https POST

Describe the solution you'd like Maybe add an easy to use configurable user interface to build such Integrations and along with a feature to view all the request / response logs for traceability.

Describe alternatives you've considered

Additional context Since keeping integrations in the application layer can be tricky some cases leading to data inconsistency - it is always fail safe to handle data integrations closer to the DB right before a CRUD operation.

A usecase would be to send data generated in a legacy system to a new system

Using PG13:

Any query through Readyset that attempts to select a UUID column seems to result in the following type of error:

ERROR:  internal error: could not retrieve expected column index 0 from row while parsing psql result: error deserializing column 0: cannot convert between the Rust type `noria_data::DataType` and the Postgres type `uuid`

Ie, for a table that looks like:

CREATE TABLE books (
    id uuid DEFAULT uuid_generate_v4() PRIMARY KEY,
    title text NOT NULL
)

select id, title from books -- query will result in the above error

select title from books -- query will succeed

Downloading ReadySet orchestrator Welcome to the ReadySet orchestrator.

I found an existing deployment named crmeb. We can continue with this deployment, or create a new one.

✔ Would you like to continue with the existing deployment? · no Before proceeding we need to tear down all other deployments. ✔ Tear down other deployments now? · yes Error: missing field advanced_settings at line 1 column 262

Is your feature request related to a problem? Please describe. A lot of popular CMS/Ecommerce applications are utilizing SET sql_mode="" in SELECT queries

Describe the solution you'd like Add SET String type to readyset application

Describe alternatives you've considered So far, ProxySQL can rewrite each query, but that is not a permanent solution.

Additional context Could expand application popularity and use cases

Is your feature request related to a problem? Please describe.

Support for Clickhouse DB

Additional context

With Clickhouse being primarily a large data OLAP DB, integration with it could lead to a wider adoption of ReadySet

I couldn't find anything related to this in the docs, so please correct me if I'm wrong.

Is your feature request related to a problem? Please describe.

Systems like FlightTracker/TAO at Facebook or Zanzibar at Google use tokens (tickets, zookies respectively) to put a minimum bound on the required consistency for a request. This enables read-after-write consistency guarantees for only the requests that need it, rather than having to wait for eventual consistency to asynchronously propagate.

Describe the solution you'd like

Some form of bounded consistency to address this issue or read a view as of a specific "time" (some SQL databases have an "as of system time" predicate).

Describe alternatives you've considered

N/A

Additional context

N/A

Is your feature request related to a problem? Please describe. What to do if the query is out of the cache range? readiest is a very interesting project, as I understand it, Readyset is caching the data from the backend database(mysql, Postgres), but I have a question:

1. Is the cache all the data of the database? (I understand that some data should be cached)
2. if the user's query exceeds the range of cached data, how to deal with it? Forward the user's SQL to the back-end database(mysql, Postgres) for processing?

Surrealdb is a NewSQL database. I couldn't find any cache layer for it. Surrealdb SQL is very similar to regular SQL. it's still in beta but works fine. it would be great if Readyset supports it. thanks.