Package com.mysql.cj
Enum MysqlType
java.lang.Object
java.lang.Enum<MysqlType>
com.mysql.cj.MysqlType
- All Implemented Interfaces:
java.io.Serializable
,java.lang.Comparable<MysqlType>
,java.lang.constant.Constable
,java.sql.SQLType
public enum MysqlType extends java.lang.Enum<MysqlType> implements java.sql.SQLType
-
Nested Class Summary
-
Enum Constant Summary
Enum Constants Enum Constant Description BIGINT
BIGINT[(M)] [UNSIGNED] [ZEROFILL] A large integer.BIGINT_UNSIGNED
BIGINT[(M)] UNSIGNED [ZEROFILL]BINARY
BINARY(M) The BINARY type is similar to the CHAR type, but stores binary byte strings rather than nonbinary character strings.BIT
BIT[(M)] A bit-field type.BLOB
BLOB[(M)] A BLOB column with a maximum length of 65,535 (216 - 1) bytes.BOOLEAN
BOOL, BOOLEAN These types are synonyms for TINYINT(1).CHAR
[NATIONAL] CHAR[(M)] [CHARACTER SET charset_name] [COLLATE collation_name] A fixed-length string that is always right-padded with spaces to the specified length when stored.DATE
DATE A date.DATETIME
DATETIME[(fsp)] A date and time combination.DECIMAL
DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL] A packed "exact" fixed-point number.DECIMAL_UNSIGNED
DECIMAL[(M[,D])] UNSIGNED [ZEROFILL]DOUBLE
DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL] A normal-size (double-precision) floating-point number.DOUBLE_UNSIGNED
DOUBLE[(M,D)] UNSIGNED [ZEROFILL]ENUM
ENUM('value1','value2',...) [CHARACTER SET charset_name] [COLLATE collation_name] An enumeration.FLOAT
FLOAT[(M,D)] [UNSIGNED] [ZEROFILL] A small (single-precision) floating-point number.FLOAT_UNSIGNED
FLOAT[(M,D)] UNSIGNED [ZEROFILL]GEOMETRY
Top class for Spatial Data Types Protocol: FIELD_TYPE_GEOMETRY = 255INT
INT[(M)] [UNSIGNED] [ZEROFILL] A normal-size integer.INT_UNSIGNED
INT[(M)] UNSIGNED [ZEROFILL]JSON
The size of JSON documents stored in JSON columns is limited to the value of the max_allowed_packet system variable (max value 1073741824).LONGBLOB
LONGBLOB A BLOB column with a maximum length of 4,294,967,295 or 4GB (232 - 1) bytes.LONGTEXT
LONGTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 4,294,967,295 or 4GB (232 - 1) characters.MEDIUMBLOB
MEDIUMBLOB A BLOB column with a maximum length of 16,777,215 (224 - 1) bytes.MEDIUMINT
MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL] A medium-sized integer.MEDIUMINT_UNSIGNED
MEDIUMINT[(M)] UNSIGNED [ZEROFILL]MEDIUMTEXT
MEDIUMTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 16,777,215 (224 - 1) characters.NULL
FIELD_TYPE_NULL = 6SET
SET('value1','value2',...) [CHARACTER SET charset_name] [COLLATE collation_name] A set.SMALLINT
SMALLINT[(M)] [UNSIGNED] [ZEROFILL] A small integer.SMALLINT_UNSIGNED
SMALLINT[(M)] UNSIGNED [ZEROFILL]TEXT
TEXT[(M)] [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 65,535 (216 - 1) characters.TIME
TIME[(fsp)] A time.TIMESTAMP
TIMESTAMP[(fsp)] A timestamp.TINYBLOB
TINYBLOB A BLOB column with a maximum length of 255 (28 - 1) bytes.TINYINT
TINYINT[(M)] [UNSIGNED] [ZEROFILL] A very small integer.TINYINT_UNSIGNED
TINYINT[(M)] UNSIGNED [ZEROFILL]TINYTEXT
TINYTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 255 (28 - 1) characters.UNKNOWN
Fall-back type for those MySQL data types which c/J can't recognize.VARBINARY
VARBINARY(M) The VARBINARY type is similar to the VARCHAR type, but stores binary byte strings rather than nonbinary character strings.VARCHAR
[NATIONAL] VARCHAR(M) [CHARACTER SET charset_name] [COLLATE collation_name] A variable-length string.YEAR
YEAR[(4)] A year in four-digit format. -
Field Summary
-
Method Summary
Modifier and Type Method Description static MysqlType
getByJdbcType(int jdbcType)
static MysqlType
getByName(java.lang.String fullMysqlTypeName)
Get MysqlType matching the full MySQL type name, for example "DECIMAL(5,3) UNSIGNED ZEROFILL".java.lang.String
getClassName()
java.lang.String
getCreateParams()
int
getJdbcType()
java.lang.String
getName()
java.lang.Long
getPrecision()
The PRECISION column represents the maximum column size that the server supports for the given datatype.java.lang.String
getVendor()
java.lang.Integer
getVendorTypeNumber()
boolean
isAllowed(int flag)
boolean
isDecimal()
Checks if the MySQL Type is a Decimal/Number Typestatic boolean
isSigned(MysqlType type)
static boolean
supportsConvert(int fromType, int toType)
Is CONVERT between the given SQL types supported?static MysqlType
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name.static MysqlType[]
values()
Returns an array containing the constants of this enum type, in the order they are declared.
-
Enum Constant Details
-
DECIMAL
DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL] A packed "exact" fixed-point number. M is the total number of digits (the precision) and D is the number of digits after the decimal point (the scale). The decimal point and (for negative numbers) the "-" sign are not counted in M. If D is 0, values have no decimal point or fractional part. The maximum number of digits (M) for DECIMAL is 65. The maximum number of supported decimals (D) is 30. If D is omitted, the default is 0. If M is omitted, the default is 10. Protocol: FIELD_TYPE_DECIMAL = 0 Protocol: FIELD_TYPE_NEWDECIMAL = 246 These types are synonyms for DECIMAL: DEC[(M[,D])] [UNSIGNED] [ZEROFILL], NUMERIC[(M[,D])] [UNSIGNED] [ZEROFILL], FIXED[(M[,D])] [UNSIGNED] [ZEROFILL] -
DECIMAL_UNSIGNED
DECIMAL[(M[,D])] UNSIGNED [ZEROFILL]- See Also:
DECIMAL
-
TINYINT
TINYINT[(M)] [UNSIGNED] [ZEROFILL] A very small integer. The signed range is -128 to 127. The unsigned range is 0 to 255. Protocol: FIELD_TYPE_TINY = 1 -
TINYINT_UNSIGNED
TINYINT[(M)] UNSIGNED [ZEROFILL]- See Also:
TINYINT
-
BOOLEAN
BOOL, BOOLEAN These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true BOOLEAN is converted to TINYINT(1) during DDL execution i.e. it has the same precision=3. Thus we have to look at full data type name and convert TINYINT to BOOLEAN (or BIT) if it has "(1)" length specification. Protocol: FIELD_TYPE_TINY = 1 -
SMALLINT
SMALLINT[(M)] [UNSIGNED] [ZEROFILL] A small integer. The signed range is -32768 to 32767. The unsigned range is 0 to 65535. Protocol: FIELD_TYPE_SHORT = 2 -
SMALLINT_UNSIGNED
SMALLINT[(M)] UNSIGNED [ZEROFILL]- See Also:
SMALLINT
-
INT
INT[(M)] [UNSIGNED] [ZEROFILL] A normal-size integer. The signed range is -2147483648 to 2147483647. The unsigned range is 0 to 4294967295. Protocol: FIELD_TYPE_LONG = 3 INTEGER[(M)] [UNSIGNED] [ZEROFILL] is a synonym for INT. -
INT_UNSIGNED
INT[(M)] UNSIGNED [ZEROFILL]- See Also:
INT
-
FLOAT
FLOAT[(M,D)] [UNSIGNED] [ZEROFILL] A small (single-precision) floating-point number. Permissible values are -3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to 3.402823466E+38. These are the theoretical limits, based on the IEEE standard. The actual range might be slightly smaller depending on your hardware or operating system. M is the total number of digits and D is the number of digits following the decimal point. If M and D are omitted, values are stored to the limits permitted by the hardware. A single-precision floating-point number is accurate to approximately 7 decimal places. Protocol: FIELD_TYPE_FLOAT = 4 Additionally: FLOAT(p) [UNSIGNED] [ZEROFILL] A floating-point number. p represents the precision in bits, but MySQL uses this value only to determine whether to use FLOAT or DOUBLE for the resulting data type. If p is from 0 to 24, the data type becomes FLOAT with no M or D values. If p is from 25 to 53, the data type becomes DOUBLE with no M or D values. The range of the resulting column is the same as for the single-precision FLOAT or double-precision DOUBLE data types. -
FLOAT_UNSIGNED
FLOAT[(M,D)] UNSIGNED [ZEROFILL]- See Also:
FLOAT
-
DOUBLE
DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL] A normal-size (double-precision) floating-point number. Permissible values are -1.7976931348623157E+308 to -2.2250738585072014E-308, 0, and 2.2250738585072014E-308 to 1.7976931348623157E+308. These are the theoretical limits, based on the IEEE standard. The actual range might be slightly smaller depending on your hardware or operating system. M is the total number of digits and D is the number of digits following the decimal point. If M and D are omitted, values are stored to the limits permitted by the hardware. A double-precision floating-point number is accurate to approximately 15 decimal places. Protocol: FIELD_TYPE_DOUBLE = 5 These types are synonyms for DOUBLE: DOUBLE PRECISION[(M,D)] [UNSIGNED] [ZEROFILL], REAL[(M,D)] [UNSIGNED] [ZEROFILL]. Exception: If the REAL_AS_FLOAT SQL mode is enabled, REAL is a synonym for FLOAT rather than DOUBLE. -
DOUBLE_UNSIGNED
DOUBLE[(M,D)] UNSIGNED [ZEROFILL]- See Also:
DOUBLE
-
NULL
FIELD_TYPE_NULL = 6 -
TIMESTAMP
TIMESTAMP[(fsp)] A timestamp. The range is '1970-01-01 00:00:01.000000' UTC to '2038-01-19 03:14:07.999999' UTC. TIMESTAMP values are stored as the number of seconds since the epoch ('1970-01-01 00:00:00' UTC). A TIMESTAMP cannot represent the value '1970-01-01 00:00:00' because that is equivalent to 0 seconds from the epoch and the value 0 is reserved for representing '0000-00-00 00:00:00', the "zero" TIMESTAMP value. An optional fsp value in the range from 0 to 6 may be given to specify fractional seconds precision. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. Protocol: FIELD_TYPE_TIMESTAMP = 7 -
BIGINT
BIGINT[(M)] [UNSIGNED] [ZEROFILL] A large integer. The signed range is -9223372036854775808 to 9223372036854775807. The unsigned range is 0 to 18446744073709551615. Protocol: FIELD_TYPE_LONGLONG = 8 SERIAL is an alias for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE. -
BIGINT_UNSIGNED
BIGINT[(M)] UNSIGNED [ZEROFILL]- See Also:
BIGINT
-
MEDIUMINT
MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL] A medium-sized integer. The signed range is -8388608 to 8388607. The unsigned range is 0 to 16777215. Protocol: FIELD_TYPE_INT24 = 9 -
MEDIUMINT_UNSIGNED
MEDIUMINT[(M)] UNSIGNED [ZEROFILL]- See Also:
MEDIUMINT
-
DATE
DATE A date. The supported range is '1000-01-01' to '9999-12-31'. MySQL displays DATE values in 'YYYY-MM-DD' format, but permits assignment of values to DATE columns using either strings or numbers. Protocol: FIELD_TYPE_DATE = 10 -
TIME
TIME[(fsp)] A time. The range is '-838:59:59.000000' to '838:59:59.000000'. MySQL displays TIME values in 'HH:MM:SS[.fraction]' format, but permits assignment of values to TIME columns using either strings or numbers. An optional fsp value in the range from 0 to 6 may be given to specify fractional seconds precision. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. Protocol: FIELD_TYPE_TIME = 11 -
DATETIME
DATETIME[(fsp)] A date and time combination. The supported range is '1000-01-01 00:00:00.000000' to '9999-12-31 23:59:59.999999'. MySQL displays DATETIME values in 'YYYY-MM-DD HH:MM:SS[.fraction]' format, but permits assignment of values to DATETIME columns using either strings or numbers. An optional fsp value in the range from 0 to 6 may be given to specify fractional seconds precision. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. Protocol: FIELD_TYPE_DATETIME = 12 -
YEAR
YEAR[(4)] A year in four-digit format. MySQL displays YEAR values in YYYY format, but permits assignment of values to YEAR columns using either strings or numbers. Values display as 1901 to 2155, and 0000. Protocol: FIELD_TYPE_YEAR = 13 -
VARCHAR
[NATIONAL] VARCHAR(M) [CHARACTER SET charset_name] [COLLATE collation_name] A variable-length string. M represents the maximum column length in characters. The range of M is 0 to 65,535. The effective maximum length of a VARCHAR is subject to the maximum row size (65,535 bytes, which is shared among all columns) and the character set used. For example, utf8 characters can require up to three bytes per character, so a VARCHAR column that uses the utf8 character set can be declared to be a maximum of 21,844 characters. MySQL stores VARCHAR values as a 1-byte or 2-byte length prefix plus data. The length prefix indicates the number of bytes in the value. A VARCHAR column uses one length byte if values require no more than 255 bytes, two length bytes if values may require more than 255 bytes. Note MySQL 5.7 follows the standard SQL specification, and does not remove trailing spaces from VARCHAR values. VARCHAR is shorthand for CHARACTER VARYING. NATIONAL VARCHAR is the standard SQL way to define that a VARCHAR column should use some predefined character set. MySQL 4.1 and up uses utf8 as this predefined character set. NVARCHAR is shorthand for NATIONAL VARCHAR. Protocol: FIELD_TYPE_VARCHAR = 15 Protocol: FIELD_TYPE_VAR_STRING = 253 -
VARBINARY
VARBINARY(M) The VARBINARY type is similar to the VARCHAR type, but stores binary byte strings rather than nonbinary character strings. M represents the maximum column length in bytes. Protocol: FIELD_TYPE_VARCHAR = 15 Protocol: FIELD_TYPE_VAR_STRING = 253 -
BIT
BIT[(M)] A bit-field type. M indicates the number of bits per value, from 1 to 64. The default is 1 if M is omitted. Protocol: FIELD_TYPE_BIT = 16 -
JSON
The size of JSON documents stored in JSON columns is limited to the value of the max_allowed_packet system variable (max value 1073741824). (While the server manipulates a JSON value internally in memory, it can be larger; the limit applies when the server stores it.) Protocol: FIELD_TYPE_BIT = 245 -
ENUM
ENUM('value1','value2',...) [CHARACTER SET charset_name] [COLLATE collation_name] An enumeration. A string object that can have only one value, chosen from the list of values 'value1', 'value2', ..., NULL or the special '' error value. ENUM values are represented internally as integers. An ENUM column can have a maximum of 65,535 distinct elements. (The practical limit is less than 3000.) A table can have no more than 255 unique element list definitions among its ENUM and SET columns considered as a group Protocol: FIELD_TYPE_ENUM = 247 -
SET
SET('value1','value2',...) [CHARACTER SET charset_name] [COLLATE collation_name] A set. A string object that can have zero or more values, each of which must be chosen from the list of values 'value1', 'value2', ... SET values are represented internally as integers. A SET column can have a maximum of 64 distinct members. A table can have no more than 255 unique element list definitions among its ENUM and SET columns considered as a group Protocol: FIELD_TYPE_SET = 248 -
TINYBLOB
TINYBLOB A BLOB column with a maximum length of 255 (28 - 1) bytes. Each TINYBLOB value is stored using a 1-byte length prefix that indicates the number of bytes in the value. Protocol:FIELD_TYPE_TINY_BLOB = 249 -
TINYTEXT
TINYTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 255 (28 - 1) characters. The effective maximum length is less if the value contains multibyte characters. Each TINYTEXT value is stored using a 1-byte length prefix that indicates the number of bytes in the value. Protocol:FIELD_TYPE_TINY_BLOB = 249 -
MEDIUMBLOB
MEDIUMBLOB A BLOB column with a maximum length of 16,777,215 (224 - 1) bytes. Each MEDIUMBLOB value is stored using a 3-byte length prefix that indicates the number of bytes in the value. Protocol: FIELD_TYPE_MEDIUM_BLOB = 250 -
MEDIUMTEXT
MEDIUMTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 16,777,215 (224 - 1) characters. The effective maximum length is less if the value contains multibyte characters. Each MEDIUMTEXT value is stored using a 3-byte length prefix that indicates the number of bytes in the value. Protocol: FIELD_TYPE_MEDIUM_BLOB = 250 -
LONGBLOB
LONGBLOB A BLOB column with a maximum length of 4,294,967,295 or 4GB (232 - 1) bytes. The effective maximum length of LONGBLOB columns depends on the configured maximum packet size in the client/server protocol and available memory. Each LONGBLOB value is stored using a 4-byte length prefix that indicates the number of bytes in the value. Protocol: FIELD_TYPE_LONG_BLOB = 251 -
LONGTEXT
LONGTEXT [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 4,294,967,295 or 4GB (232 - 1) characters. The effective maximum length is less if the value contains multibyte characters. The effective maximum length of LONGTEXT columns also depends on the configured maximum packet size in the client/server protocol and available memory. Each LONGTEXT value is stored using a 4-byte length prefix that indicates the number of bytes in the value. Protocol: FIELD_TYPE_LONG_BLOB = 251 -
BLOB
BLOB[(M)] A BLOB column with a maximum length of 65,535 (216 - 1) bytes. Each BLOB value is stored using a 2-byte length prefix that indicates the number of bytes in the value. An optional length M can be given for this type. If this is done, MySQL creates the column as the smallest BLOB type large enough to hold values M bytes long. Protocol: FIELD_TYPE_BLOB = 252 -
TEXT
TEXT[(M)] [CHARACTER SET charset_name] [COLLATE collation_name] A TEXT column with a maximum length of 65,535 (216 - 1) characters. The effective maximum length is less if the value contains multibyte characters. Each TEXT value is stored using a 2-byte length prefix that indicates the number of bytes in the value. An optional length M can be given for this type. If this is done, MySQL creates the column as the smallest TEXT type large enough to hold values M characters long. Protocol: FIELD_TYPE_BLOB = 252 -
CHAR
[NATIONAL] CHAR[(M)] [CHARACTER SET charset_name] [COLLATE collation_name] A fixed-length string that is always right-padded with spaces to the specified length when stored. M represents the column length in characters. The range of M is 0 to 255. If M is omitted, the length is 1. Note Trailing spaces are removed when CHAR values are retrieved unless the PAD_CHAR_TO_FULL_LENGTH SQL mode is enabled. CHAR is shorthand for CHARACTER. NATIONAL CHAR (or its equivalent short form, NCHAR) is the standard SQL way to define that a CHAR column should use some predefined character set. MySQL 4.1 and up uses utf8 as this predefined character set. MySQL permits you to create a column of type CHAR(0). This is useful primarily when you have to be compliant with old applications that depend on the existence of a column but that do not actually use its value. CHAR(0) is also quite nice when you need a column that can take only two values: A column that is defined as CHAR(0) NULL occupies only one bit and can take only the values NULL and '' (the empty string). Protocol: FIELD_TYPE_STRING = 254 -
BINARY
BINARY(M) The BINARY type is similar to the CHAR type, but stores binary byte strings rather than nonbinary character strings. M represents the column length in bytes. The CHAR BYTE data type is an alias for the BINARY data type. Protocol: no concrete type on the wire TODO: really? -
GEOMETRY
Top class for Spatial Data Types Protocol: FIELD_TYPE_GEOMETRY = 255 -
UNKNOWN
Fall-back type for those MySQL data types which c/J can't recognize. Handled the same as BLOB. Has no protocol ID.
-
-
Field Details
-
jdbcType
protected int jdbcType -
javaClass
protected final java.lang.Class<?> javaClass -
FIELD_FLAG_NOT_NULL
public static final int FIELD_FLAG_NOT_NULL- See Also:
- Constant Field Values
-
FIELD_FLAG_PRIMARY_KEY
public static final int FIELD_FLAG_PRIMARY_KEY- See Also:
- Constant Field Values
-
FIELD_FLAG_UNIQUE_KEY
public static final int FIELD_FLAG_UNIQUE_KEY- See Also:
- Constant Field Values
-
FIELD_FLAG_MULTIPLE_KEY
public static final int FIELD_FLAG_MULTIPLE_KEY- See Also:
- Constant Field Values
-
FIELD_FLAG_BLOB
public static final int FIELD_FLAG_BLOB- See Also:
- Constant Field Values
-
FIELD_FLAG_UNSIGNED
public static final int FIELD_FLAG_UNSIGNED- See Also:
- Constant Field Values
-
FIELD_FLAG_ZEROFILL
public static final int FIELD_FLAG_ZEROFILL- See Also:
- Constant Field Values
-
FIELD_FLAG_BINARY
public static final int FIELD_FLAG_BINARY- See Also:
- Constant Field Values
-
FIELD_FLAG_AUTO_INCREMENT
public static final int FIELD_FLAG_AUTO_INCREMENT- See Also:
- Constant Field Values
-
FIELD_TYPE_DECIMAL
public static final int FIELD_TYPE_DECIMAL- See Also:
- Constant Field Values
-
FIELD_TYPE_TINY
public static final int FIELD_TYPE_TINY- See Also:
- Constant Field Values
-
FIELD_TYPE_SHORT
public static final int FIELD_TYPE_SHORT- See Also:
- Constant Field Values
-
FIELD_TYPE_LONG
public static final int FIELD_TYPE_LONG- See Also:
- Constant Field Values
-
FIELD_TYPE_FLOAT
public static final int FIELD_TYPE_FLOAT- See Also:
- Constant Field Values
-
FIELD_TYPE_DOUBLE
public static final int FIELD_TYPE_DOUBLE- See Also:
- Constant Field Values
-
FIELD_TYPE_NULL
public static final int FIELD_TYPE_NULL- See Also:
- Constant Field Values
-
FIELD_TYPE_TIMESTAMP
public static final int FIELD_TYPE_TIMESTAMP- See Also:
- Constant Field Values
-
FIELD_TYPE_LONGLONG
public static final int FIELD_TYPE_LONGLONG- See Also:
- Constant Field Values
-
FIELD_TYPE_INT24
public static final int FIELD_TYPE_INT24- See Also:
- Constant Field Values
-
FIELD_TYPE_DATE
public static final int FIELD_TYPE_DATE- See Also:
- Constant Field Values
-
FIELD_TYPE_TIME
public static final int FIELD_TYPE_TIME- See Also:
- Constant Field Values
-
FIELD_TYPE_DATETIME
public static final int FIELD_TYPE_DATETIME- See Also:
- Constant Field Values
-
FIELD_TYPE_YEAR
public static final int FIELD_TYPE_YEAR- See Also:
- Constant Field Values
-
FIELD_TYPE_VARCHAR
public static final int FIELD_TYPE_VARCHAR- See Also:
- Constant Field Values
-
FIELD_TYPE_BIT
public static final int FIELD_TYPE_BIT- See Also:
- Constant Field Values
-
FIELD_TYPE_JSON
public static final int FIELD_TYPE_JSON- See Also:
- Constant Field Values
-
FIELD_TYPE_NEWDECIMAL
public static final int FIELD_TYPE_NEWDECIMAL- See Also:
- Constant Field Values
-
FIELD_TYPE_ENUM
public static final int FIELD_TYPE_ENUM- See Also:
- Constant Field Values
-
FIELD_TYPE_SET
public static final int FIELD_TYPE_SET- See Also:
- Constant Field Values
-
FIELD_TYPE_TINY_BLOB
public static final int FIELD_TYPE_TINY_BLOB- See Also:
- Constant Field Values
-
FIELD_TYPE_MEDIUM_BLOB
public static final int FIELD_TYPE_MEDIUM_BLOB- See Also:
- Constant Field Values
-
FIELD_TYPE_LONG_BLOB
public static final int FIELD_TYPE_LONG_BLOB- See Also:
- Constant Field Values
-
FIELD_TYPE_BLOB
public static final int FIELD_TYPE_BLOB- See Also:
- Constant Field Values
-
FIELD_TYPE_VAR_STRING
public static final int FIELD_TYPE_VAR_STRING- See Also:
- Constant Field Values
-
FIELD_TYPE_STRING
public static final int FIELD_TYPE_STRING- See Also:
- Constant Field Values
-
FIELD_TYPE_GEOMETRY
public static final int FIELD_TYPE_GEOMETRY- See Also:
- Constant Field Values
-
-
Method Details
-
values
Returns an array containing the constants of this enum type, in the order they are declared.- Returns:
- an array containing the constants of this enum type, in the order they are declared
-
valueOf
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)- Parameters:
name
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is null
-
getByName
Get MysqlType matching the full MySQL type name, for example "DECIMAL(5,3) UNSIGNED ZEROFILL". Distinct *_UNSIGNED type will be returned if "UNSIGNED" is present in fullMysqlTypeName.- Parameters:
fullMysqlTypeName
- full MySQL type name- Returns:
- MysqlType
-
getByJdbcType
-
supportsConvert
public static boolean supportsConvert(int fromType, int toType)Is CONVERT between the given SQL types supported?- Parameters:
fromType
- the type to convert fromtoType
- the type to convert to- Returns:
- true if so
- See Also:
Types
-
isSigned
-
getName
public java.lang.String getName()- Specified by:
getName
in interfacejava.sql.SQLType
-
getJdbcType
public int getJdbcType() -
isAllowed
public boolean isAllowed(int flag) -
getClassName
public java.lang.String getClassName() -
isDecimal
public boolean isDecimal()Checks if the MySQL Type is a Decimal/Number Type- Returns:
- true if the MySQL Type is a Decimal/Number Type
-
getPrecision
public java.lang.Long getPrecision()The PRECISION column represents the maximum column size that the server supports for the given datatype.- For numeric data, this is the maximum precision.
- For character data, this is the length in characters.
- For datetime datatypes, this is the length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component).
- For binary data, this is the length in bytes.
- For the ROWID datatype, this is the length in bytes.
- Null is returned for data types where the column size is not applicable.
- Returns:
- precision
-
getCreateParams
public java.lang.String getCreateParams() -
getVendor
public java.lang.String getVendor()- Specified by:
getVendor
in interfacejava.sql.SQLType
-
getVendorTypeNumber
public java.lang.Integer getVendorTypeNumber()- Specified by:
getVendorTypeNumber
in interfacejava.sql.SQLType
-