Marcelo Altmann

**Description** In case we fail to Parse a DDL, we show the reason why, but we don't mention which table was erroring out: ``` 2024-06-25T16:47:23.003371Z WARN taking database snapshot: replicators::mysql_connector::snapshot:...

**Description** Currently when snapshotting, we require to replicate all tables from FK's example: ``` CREATE TABLE c (ID INT PRIMARY KEY); CREATE TABLE b (ID INT PRIMARY KEY, c_ID INT,...

**Description** If a user has a lot of tables to replicate and does not want to replicate all, they might use replication filters to not snapshot some tables. Currently SHOW...

**Description** In case we fail to Parse a DDL, we show the reason why, but we don't mention which table was erroring out: ``` 2024-06-25T16:47:23.003371Z WARN taking database snapshot: replicators::mysql_connector::snapshot:...

**Description** Currently when snapshotting, we require to replicate all tables from FK's example: ``` CREATE TABLE c (ID INT PRIMARY KEY); CREATE TABLE b (ID INT PRIMARY KEY, c_ID INT,...

**Description** If a user has a lot of tables to replicate and does not want to replicate all, they might use replication filters to not snapshot some tables. Currently SHOW...

**Description** Ensure readyset uses --upstream-db-url user for replication and --username/--password for application usage **Change in user-visible behavior** **Requires documentation change**

**Description** MySQL stores timestamp internally as UTC and convert them to timezone specified at `time_zone` variable. During snapshot we are getting the correct value for timestamp fields as we are...

**Description** Sport this while testing perf of hash joins for straddle joins. If we have a cache and then restart readyset, when the migration is happening and we keep running...

**Description** We currently fail to parse HEX values: ``` CREATE TABLE t (name VARCHAR(10)); INSERT INTO t VALUES (0x6D617263656C6F); readyset> SELECT * FROM t WHERE name = 0x6D617263656C6F; +---------+ |...