Amazon Aurora for MySQL 5.7 Adapter Limitations

Supported Types
Read Table
Execute Select SQL
Write Table
Execute Update SQL
Execute Stored Procedure
Major Exceptions

Supported Types

The types supported in this adapter are the following.

Type name	Support	Remarks
BOOL (BOOLEAN)	Yes	Alias of tinyint(1)
BIT	Limited
TINYINT	Yes
TINYINT UNSIGNED	Limited
MEDIUMINT	Yes
MEDIUMINT UNSIGNED	Limited
SMALLINT	Yes
SMALLINT UNSIGNED	Limited
INT (INTEGER)	Yes
INT UNSIGNED (INTEGER UNSIGNED)	Limited
BIGINT	Yes
BIGINT UNSIGNED	Limited
FLOAT	Limited
FLOAT UNSIGNED	Limited
DOUBLE	Limited
DOUBLE UNSIGNED	Limited
REAL	Limited
REAL UNSIGNED	Limited
DECIMAL (NUMERIC)	Yes
DECIMAL UNSIGNED (NUMERIC UNSIGNED)	Limited
DATE	Limited
DATETIME	Limited
TIMESTAMP	Limited
TIME	Limited
YEAR	Limited
CHAR	Limited
VARCHAR	Limited
BINARY	Yes
VARBINARY	Yes
TINYBLOB	Yes
TINYTEXT	Limited
BLOB	Yes
TEXT	Limited
MEDIUMBLOB	Yes
MEDIUMTEXT	Limited
LONGBLOB	Yes
LONGTEXT	Limited
ENUM	Limited
SET	Limited
JSON	No

Yes: Supported.
Limited: Supported with limitations.
No: Not supported.

Read Table

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type data are not supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
- If the number of digits is large, the correct value cannot be retrieved.
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
DATE, DATETIME, TIMESTAMP
- When data is 0000-00-00 00:00:00, it will be retrieved as null.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  Example: if the data is "27:15:00", it will be "03:15:00".
  Example: if the data is "-04:20:00", it will be "20:20:00 PM". It will not be "19:40:00".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DOUBLE UNSIGNED
- It is displayed without UNSIGNED in [Schema definition/Type].
Even when an optional extended attribute ZEROFILL is specified, the result is returned excluding 0.

Default value of [Fetch size] is 500.

Execute Select SQL

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type data are not supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
- If the number of digits is large, the correct value cannot be retrieved.
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
DATE, DATETIME, TIMESTAMP
- When data is 0000-00-00 00:00:00, it will be retrieved as null.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  Example: if the data is "27:15:00", it will be "03:15:00".
  Example: if the data is "-04:20:00", it will be "20:20:00". It will not be "19:40:00".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DOUBLE UNSIGNED
- It is displayed without UNSIGNED in [Output schema definition/Type].
Even when an optional extended attribute ZEROFILL is specified, the result is returned excluding 0.

Default value of [Fetch size] is 500.

Write Table

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type data are not supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
- Values nearby the maximum value or the minimum value cannot be written.
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
DATE, DATETIME, TIMESTAMP
- In the case of non-existent date, it is not written correctly.
  Example: When the date is “0000/00/00”, it will be “0002/11/30”.
TIME
- If the epoch second of time is negative value, it will not be written correctly.
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DOUBLE UNSIGNED
- It is displayed without UNSIGNED in [Schema definition/Type].

Execute Update SQL

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type data are not supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
- Values nearby the maximum value or the minimum value cannot be written.
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
DATE, DATETIME, TIMESTAMP
- In the case of non-existent date, it is not written correctly.
  Example: When the date is “0000/00/00”, it will be “0002/11/30”.
TIME
- If the epoch second of time is negative value, it will not be written correctly.
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.

Execute Stored Procedure

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type data are not supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
- If the number of digits is large, the correct value cannot be retrieved.
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
- Values nearby the maximum value or the minimum value cannot be written.
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  For more details, refer to “MySQL Reference Manual” (https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html).
CHAR, VARCHAR, TEXT, TINYTEXT, MEDIUMTEXT, LONGTEXT
- An error occurs when an argument with multi-byte characters is used.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  Example: if the data is "27:15:00", it will be "03:15:00".
  Example: if the data is "-04:20:00", it will be "20:20:00 PM". It will not be "19:40:00".
- If the epoch second of time is negative value, it will not be written correctly.
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.
ENUM, SET
- An error occurs when an argument with multi-byte characters is used.
TINYINT UNSIGNED, MEDIUMINT UNSIGNED, SMALLINT UNSIGNED, INT UNSIGNED, BIGINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DECIMAL UNSIGNED
- It is displayed without UNSIGNED in [Input/Type] and [Output/Type].

Major Exceptions

Exception name		Cause	Solution
java.sql.SQLNonTransientConnectionException		Unable to connect to the database.	Check [Cluster Endpoint] or [Port number] of the global resource.
java.sql.SQLException	Communications link failure with primary. No active connection found for master. Caused by: java.sql.SQLException: Access denied for user '<user name>'@'%' to database '<database name>'	The database is not found.	Specify an existing database in [Database name] of global resource.
java.sql.SQLException	Communications link failure with primary. No active connection found for master. java.sql.SQLException: Access denied for user '<user name>'@'<IP address>' (using password: YES)	The user name, the password or the SSL connection is incorrect.	Check [User name], [Password] or [SSL connection] of the global resource.
java.sql.SQLSyntaxErrorException	Table '<table name>' doesn't exist	The table does not exist.	Specify an existing table in [Table name].