| Wiki Markup | |
|---|---|
| Panel | |
|
Upgrade of Packaged MySQL JDBC Connector to 8.0.x
...
This
...
update
...
affects
...
users
...
using
...
MySQL
...
as
...
the
...
Universal
...
Controller
...
Database,
...
or
...
have
...
SQL
...
/
...
Stored
...
Procedure
...
Tasks
...
that
...
run
...
against
...
MySQL
...
databases.
...
If
...
you
...
use
...
MySQL
...
as
...
the
...
Universal
...
Controller
...
Database,
...
or
...
have
...
SQL
...
/
...
Stored
...
Procedure
...
Tasks
...
that
...
run
...
against
...
MySQL
...
databases,
...
you
...
should
...
review
...
the
...
MySQL
...
JDBC
...
Connector
...
8.0
...
upgrade
...
information
...
before
...
upgrading
...
to
...
UC
...
6.4.7.0.
...
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-upgrading-to-8.0.html
...
It is important to note that we have observed the following changes in behavior with the new MySQL JDBC Connector:
Change 1
If the SQL Task Instance or Stored Procedure Task Instance is currently processing the SLEEP(\n)
...
function
...
at
...
the
...
time
...
a
...
cancel
...
is
...
attempted,
...
depending
...
on
...
the
...
SQL
...
statement,
...
a
...
MySQLStatementCancelledException
...
may
...
no
...
longer
...
be
...
thrown,
...
meaning
...
the
...
SQL
...
Task
...
Instance
...
or
...
Stored
...
Procedure
...
Task
...
Instance
...
will
...
immediately
...
transition
...
to
...
Success
...
from
...
Cancel
...
Pending,
...
rather
...
than
...
transitioning
...
to
...
Cancelled.
...
For
...
example:
...
If cancelled,
...
the
...
following
...
SQL
...
Task
...
Instance
...
SQL
...
Command
...
would
...
complete
...
with
...
status
...
Success.
...
| Panel | |||
|---|---|---|---|
|
If cancelled,
...
the
...
following
...
SQL
...
Task
...
Instance
...
SQL
...
Command
...
would
...
complete
...
with
...
status
...
Cancelled.
...
| Panel | ||||
|---|---|---|---|---|
|
For
...
more
...
information
...
on
...
the
...
SLEEP
...
function,
...
please
...
see
...
the
...
MySQL
...
documentation
...
here:
...
https://dev.mysql.com/doc/refman/5.6/en/miscellaneous-functions.html#function_sleep
...
Change 2
If the server time zone value is unrecognized or represents more than one time zone, you must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specific time zone value if you want to utilize time zone support.
We recommended adding the following parameter to the Connection URL: &serverTimezone=UTC (or alternatively, a preferred timezone, such as &serverTimezone=America/New_York).