Bug #27156 Not even if strict mode will halt on warnings
Submitted: 14 Mar 2007 23:33 Modified: 6 Nov 2010 17:37
Reporter: Stephen Gornick Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Data Types Severity:S3 (Non-critical)
Version:5.0, 5.1, 5.6.99 OS:Linux (Linux)
Assigned to: CPU Architecture:Any
Tags: client, client, error, errors, execute, Execution, force, halt, halted, mode, mode, SQL, sql mode, SQL_MODE, stop, stopped, strict, strict mode, strict_all_tables, strict_trans_tables, traditional, warning, warnings

File: Maximum allowed size is 3MB.

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-27156.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:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: 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.

[14 Mar 2007 23:43] Stephen Gornick

Attachment: test.sql (application/octet-stream, text), 410 bytes.