Marcelo Altmann

**Description** ``` # It works when you do it on a running instance (via replication) mysql> CREATE TABLE C (ID INT); Query OK, 0 rows affected (0,02 sec) mysql> CREATE...

**Description** Sometimes we will find and fix issues that will fix how we store data. One example is the recent issue with DATE field, where we were missing to set...

**Description** When a primary database goes does, one of the secondaries will take over and be promoted to the primary. Readyset should be able to adjust to the new primary,...

**Description** There are some external tools such as ProxySQL/Grafana, that require fetching the status of Readyset, such as `SHOW READYSET STATUS`, `SHOW CACHES`, `SHOW PROXIED QUERIES`. Currently we need to...

**Description** Investigate why we are not incrementing readyset_query_log_total_cache_misses counter when we hit a cache miss. Example of one deployment with two caches: ``` # TYPE readyset_server_view_query_result_miss counter 0 readyset_server_view_query_result_miss{upstream_db_type="mysql",deployment="readyset.db"} 72611...

**Description** When connected to MySQL, Readyset is not setting the report_host and port to display on SHOW REPLICAS: ``` mysql> SHOW REPLICAS; +------------+------+------+------------+--------------+ | Server_Id | Host | Port |...

**Description** Currently we have a command `SHOW READYSET STATUS` that displays some information about the status: ``` readyset> SHOW READYSET STATUS; +----------------------------+--------------------------------------+ | Variable_name | Value | +----------------------------+--------------------------------------+ | Database...

**Description** Today we have `--unsupported-set-mode` that allows for two values, Error and Proxy. but we also have `--allow-unsupported-set` as a dedicated variable. Those two variables all control what we set...

**Description** ``` create table yy (yy year); ``` This results in : ``` 2024-08-12T22:32:58.439027Z WARN taking database snapshot: replicators::mysql_connector::snapshot: Error extending CREATE TABLE "test"."yy", table will not be used error=Query...

**Description** [https://dev.mysql.com/doc/dev/mysql-server/latest/page_protocol_com_query_response_text_resultset_column_definition.html](https://dev.mysql.com/doc/dev/mysql-server/latest/page_protocol_com_query_response_text_resultset_column_definition.html) Our protocol definition for below items differ from MySQL: * character_set * column_length * decimals * flags (out of the scope) We should fix the first 3 items...