You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files in src/Plugin/Select implement responses to different tools speaking with mysql proto.
Since some funcs going to move to daemon's code, query tests are necessary.
That is all real kinds of 'select ... from information_schema.tables' - with correct answers, which budy generates.
It should be not just general queries, but concrete specific queries dumped from the tools in real sessions.
There are some comments in the code - like 'HeidiSQL tool doesn't recognize lowercase data types so we add this extra transformation', or 'Adding the character set columns with fake data since they're mandatory for HeidiSQL'. They explain some of details, but that is much better to have whole picture. Ideally - just written sessions from different apps with buddy's answers, what is happened 'underneath'.
For now only queries to INFORMATION_SCHEMA.TABLES is necessary
As an example you can see test/test_272/test.xml. It contains real sessions from mysqldump with different params. Here is request to make same one with the tools tested with 'information_schema.tables mentioned HeidiSQL, and also all the other which was used to create the plugin.
Checklist:
To be completed by the assignee. Check off tasks that have been completed or are not applicable.
Implementation completed
Tests developed
Documentation updated
Documentation reviewed
Changelog updated
OpenAPI YAML updated and issue created to rebuild clients
The text was updated successfully, but these errors were encountered:
Proposal:
Files in src/Plugin/Select implement responses to different tools speaking with mysql proto.
Since some funcs going to move to daemon's code, query tests are necessary.
That is all real kinds of 'select ... from information_schema.tables' - with correct answers, which budy generates.
It should be not just general queries, but concrete specific queries dumped from the tools in real sessions.
There are some comments in the code - like 'HeidiSQL tool doesn't recognize lowercase data types so we add this extra transformation', or 'Adding the character set columns with fake data since they're mandatory for HeidiSQL'. They explain some of details, but that is much better to have whole picture. Ideally - just written sessions from different apps with buddy's answers, what is happened 'underneath'.
For now only queries to INFORMATION_SCHEMA.TABLES is necessary
As an example you can see test/test_272/test.xml. It contains real sessions from mysqldump with different params. Here is request to make same one with the tools tested with 'information_schema.tables mentioned HeidiSQL, and also all the other which was used to create the plugin.
Checklist:
To be completed by the assignee. Check off tasks that have been completed or are not applicable.
The text was updated successfully, but these errors were encountered: