configuring roundcube-core mysql said: ERROR: ASCII '\0' appeared in the statement, but this is not allowed unless option --binary-mode is enabled and mysql is run in non-interactive │ │ mode. Set --binary-mode to 1 if ASCII '\0' is expected. Query: 'b0VIM 8.0'.

[timeless]

do-release-upgrade from xenial to bionic

2021-04-11 02:29:03 upgrade roundcube-core:all 1.2~beta+dfsg.1-0ubuntu1 1.3.6+dfsg.1-1

lsb_release -rd:
Description: Ubuntu 18.04.5 LTS
Release: 18.04

apt-cache policy roundcube-core:
roundcube-core:
  Installed: 1.3.6+dfsg.1-1
  Candidate: 1.3.6+dfsg.1-1
  Version table:
 *** 1.3.6+dfsg.1-1 500
        500 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

Expected results: roundcube-core successfully updates w/o issue

Actual results:

```
 ┌────────────────────────────────────────────────────────────────┤ Configuring roundcube-core ├─────────────────────────────────────────────────────────────────┐
 │ An error occurred while upgrading the database: │
 │ │
 │ mysql said: ERROR: ASCII '\0' appeared in the statement, but this is not allowed unless option --binary-mode is enabled and mysql is run in non-interactive │
 │ mode. Set --binary-mode to 1 if ASCII '\0' is expected. Query: 'b0VIM 8.0'. │
 │ │
 │ Fortunately, /var/cache/dbconfig-common/backups/roundcube_1.2~beta+dfsg.1-0ubuntu1.2021-04-11-03.24.28 should hold a backup of the database, made just │
 │ before the upgrade (unless the error occurred during backup creation, in which case no changes will have been applied yet). Your options are: │
```

I'm going to configure mariadb to use --binary-mode which I expect will resolve my issue. But it seemed worth reporting as I can't find a reference for mariadb+roundcube+"binary-mode".