Amazon RDS for MySQL 5.1 Adapter Limitations

Supported Types

Supports types for this adapter are as follows.

Type name	Support	Remarks
BOOL (BOOLEAN)	Yes	Alias of tinyint(1)
BIT	Limited
TINYINT	Yes
TINYINT UNSIGNED	Yes
MEDIUMINT	Yes
MEDIUMINT UNSIGNED	Yes
SMALLINT	Yes
SMALLINT UNSIGNED	Yes
INT (INTEGER)	Yes
INT UNSIGNED (INTEGER UNSIGNED)	Yes
BIGINT	Yes
BIGINT UNSIGNED	Yes
FLOAT	Limited
FLOAT UNSIGNED	Limited
DOUBLE	Limited
DOUBLE UNSIGNED	Limited
REAL	Limited
REAL UNSIGNED	Limited
DECIMAL (NUMERIC)	Yes
DECIMAL UNSIGNED (NUMERIC UNSIGNED)	Yes
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

BIT
- BIT data with size of 1 is treated as Boolean. Other sized BIT is not supported.
FLOAT,FLOAT UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DOUBLE,DOUBLE UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DATE,DATETIME,TIMESTAMP
- Error occurs when data is 0000-00-00 00:00:00.
TIME
- Supports the range of 00:00:00 to 23:59:59. Otherwise, error occurs.
YEAR
- Treated as String data.
Even if ZEROFILL optional extension attribute is specified, it returns results in which 0s are excluded.

BIT
- BIT data with size of 1 is treated as Boolean.Other sized BIT is not supported.
FLOAT,FLOAT UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DOUBLE,DOUBLE UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DATE,DATETIME,TIMESTAMP
- Error occurs when data is 0000-00-00 00:00:00.
TIME
- Supports the range of 00:00:00 to 23:59:59. Otherwise, error occurs.
YEAR
- Treated as String data.
Even if ZEROFILL optional extension attribute is specified, it returns results in which 0s are excluded.

BIT
- BIT data with size of 1 is treated as Boolean.Other sized BIT is not supported.
FLOAT,FLOAT UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DOUBLE,DOUBLE UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DATE,DATETIME,TIMESTAMP
- In case of the date in which data does not exist, it will not be written correctly.
  For example: "00 month 00 day, 0000" will become "November 30, 0002".
TIME
- Supports the range of 00:00:00 to 23:59:59. Otherwise, error occurs.
YEAR
- Treated as String data.

BIT
- BIT data with size of 1 is treated as Boolean.Other sized BIT is not supported.
FLOAT,FLOAT UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DOUBLE,DOUBLE UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DATE,DATETIME,TIMESTAMP
- In case of the date in which data does not exist, it will not be written correctly.
  For example: "00 month 00 day, 0000" will become "November 30, 0002".
TIME
- Supports the range of 00:00:00 to 23:59:59. Otherwise, error occurs.
YEAR
- Treated as String data.

BIT
- BIT data with size of 1 is treated as Boolean. Other sized BIT is not supported.
FLOAT,FLOAT UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
DOUBLE,DOUBLE UNSIGNED
- MySQL have some considerations related to floating point accuracy.
  For more information, refer to "MySQL Reference Manual" (the URL below). http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
CHAR,VARCHAR,TEXT,TINYTEXT,MEDIUMTEXT,LONGTEXT
- When using the argument that contains a multi-byte character, error will occur.
TIME
- Supports the range of 00:00:00 to 23:59:59. Otherwise, error occurs.
YEAR
- Treated as String data.
ENUM,SET
- When using the argument that contains a multi-byte character, error will occur.

Exception name		Causes	Solution
com.mysql.jdbc.exceptions.jdbc4.CommunicationsExceptionn		Cannot connect to database.	Make sure that [Hostname] or [Port number] in Global Resource is correct.
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException	Unknown database '<database name>'	The specified database does not exists.	Make sure that the database specified in the [Database name] in Global Resource exists.
java.sql.SQLException	Access denied for user '<user name>'@'<terminal name>'(using password: YES)	Username or password is invalid.	Make sure both [User name] and [Password] specified in Global Resource are valid.
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException	Table '<table name>' does not exist	The table specified does not exists.	Specify a table name which exists in [Table name].