Mitzasql

Changed
- Bump kramdown to 2.3.1 in /docs
- Bump pygments to 2.7.4

Fixed
- Fix crash (95)
- Fix database change error caused by accidentally mutating the original connection data when running custom query
- Fix crash when running executing invalid SQL in multi query
- Remove duplicate "Clipboard support" section in user manual
- Fix crash when viewing stored procedure without parameters

Changed
- Auto quote filter command parameters based on the column type. https://github.com/vladbalmos/mitzasql/issues/94

Fixed
- Fix 90 (Invalid filter value breaks table view screen)

Fixed
- Fix connection database name caching issue

Changed
- Switch to relative imports for consistency
- Improve test scripts to allow testing against only selected versions of mysql and python. Add `help` option
- Improve columns sizing during rendering
- Allow multiple statements to be executed in the query editor. Eg:
SET a = (SELECT ...)
SELECT a
- Ctrl-C has been re-assigned to copy text from the query editor

Added
- Smart autocomplete for common statements
- Add "Loading..." status when switching views
- Add system clipboard (ctrl c/ctrl v) support to query editor (optional dependency: pyperclip)

Fixed
- Fix a bug where a column containing spaces in its name breaks the table screen view
- Fix a bug related to caching a table view (same table name in different databases)
- Fix a bug the lead to a crash when pasting text larger than the in the query editor widget

Changed
- Switch to RawConfigParser to fix issue with percent sign in passwords (pull/86 by oliverseal)
- Drop support for Python 3.5
- Drop support for MySQL 5.5
- Upgrade to Urwid 2.1.2
- Upgrade mysql-connector-python to 8.0.22
- Upgrade appdirs to 1.4.4
- Upgrade pygments to 2.7.2
- Update documentation
- Go back to previous screen after dismissing a SQL error
- Log line numbers executed by macros
- Go back and refresh previous screen if the Query Editor runs sql which modifies records (insert, update, delete, etc...)
- Prevent caching custom queries

Fixed
- Fix for 88: Database names with dashes cause error 1064 (42000)
- Fix for 84
- Fix for 85
- Fix for 86