Bug #86163 | can't update temporary table when joined with table with triggers on read-only | ||
---|---|---|---|
Submitted: | 2 May 2017 21:29 | Modified: | 11 May 2017 9:20 |
Reporter: | Bret Westenskow | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S2 (Serious) |
Version: | All, 5.7.18 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | read only, temporary table, trigger, UPDATE |
If the data you need to attach is more than 3MB, you should create
a compressed archive of the data and a README file that describes the data
with a filename that includes the bug number (recommended filename:
mysql-bug-data-86163.zip
) and upload one to sftp.oracle.com.
A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com)
and a client that supports SFTP are required in order to access the SFTP server.
To upload the file to sftp.oracle.com:
- Open an SFTP client and connect to
sftp.oracle.com
. Specify port2021
and remote directory/support/incoming/
. - Log in with your newly created Oracle Web account (email address) and password.
- Upload the archive to
/support/incoming
. - Once you have uploaded the file, add a comment to this bug to notify us about it.
sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming
Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.