Tim Sehn
Tim Sehn
Could you change the keys to a randomly generated GUID? That model works better for Dolt than auto increment.
Merging this and #3521
I'm not sure how I triggered it. But the steps I took are in issue #3558
This happened as I was composing a query against `employees_teams`. After the panic, it disconnects from the database and I have to reconnect so this is customer facing.
I think this may have to do with the table having multiple primary keys.
Even simpler repro: ``` mysql> select * from information_schema.statistics; ERROR 1105 (HY000): panic in ExchangeIterPartitionRows: unknown message id M ```
Does not happen unless in sql-server mode: ``` getting_started $ dolt sql -q "select * from information_schema.statistics" +---------------+-----------------+-----------------+------------+-----------------+-------------+--------------+-------------+-----------+-------------+----------+--------+----------+------------+---------+---------------+------------+------------+ | table_catalog | table_schema | table_name | non_unique | index_schema | index_name...
Easy repro: 1. Start a dolt sql-server 2. Connect with a mysql client 3. Run: ``` dolt $ mysql --host 127.0.0.1 --port 3306 -uroot Welcome to the MySQL monitor. Commands...
This had to do with me having new format databases in the same directory as old format databases. information_schema needs to access every database the server can see. When it...