H2 | type-mapping und EntityGeneratorCustomizer | JAVA Beispiel | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CHARACTER(n) A Unicode String. This type is supported for compatibility with other databases and older applications. The difference to The maximum precision is is a size constraint; only the actual data is persisted. The whole text is kept in memory when using this data type. | -
|
| ||||||||||||||||||||
CHAR(n) A Unicode String. This type is supported for compatibility with other databases and older applications. The difference to The maximum precision is is a size constraint; only the actual data is persisted. The whole text is kept in memory when using this data type. | -
|
| ||||||||||||||||||||
NCHAR(n)
A Unicode String. This type is supported for compatibility with other databases and older applications. The difference to The maximum precision is is a size constraint; only the actual data is persisted. The whole text is kept in memory when using this data type. | -
|
| ||||||||||||||||||||
INT Possible values: -2147483648 to 2147483647. | - - |
| ||||||||||||||||||||
INTEGER Possible values: -2147483648 to 2147483647. | - - |
| ||||||||||||||||||||
MEDIUMINT Possible values: -2147483648 to 2147483647. | - - |
| ||||||||||||||||||||
INT4 Possible values: -2147483648 to 2147483647. | - - |
| ||||||||||||||||||||
SIGNED Possible values: -2147483648 to 2147483647. | - - |
| ||||||||||||||||||||
BOOLEAN Possible values: | - - |
| ||||||||||||||||||||
BIT Possible values: | - - |
| ||||||||||||||||||||
BOOL Possible values: | - - |
| ||||||||||||||||||||
TINYINT Possible values are: -128 to 127. | - - |
| ||||||||||||||||||||
SMALLINT Possible values: -32768 to 32767. | - - |
| ||||||||||||||||||||
INT2 Possible values: -32768 to 32767. | - - |
| ||||||||||||||||||||
YEAR Possible values: -32768 to 32767. | - - |
| ||||||||||||||||||||
BIGINT Possible values: -9223372036854775808 to 9223372036854775807. | - - |
| ||||||||||||||||||||
INT8 Possible values: -9223372036854775808 to 9223372036854775807. | - - |
| ||||||||||||||||||||
IDENTITY Auto-Increment value. Possible values: -9223372036854775808 to 9223372036854775807. Used values are never re-used, even when the transaction is rolled back. | - - |
| ||||||||||||||||||||
DECIMAL Data type with fixed precision and scale. This data type is recommended for storing currency values. | - - |
| ||||||||||||||||||||
NUMBER Data type with fixed precision and scale. This data type is recommended for storing currency values. | - - |
| ||||||||||||||||||||
DEC Data type with fixed precision and scale. This data type is recommended for storing currency values. | - - |
| ||||||||||||||||||||
NUMERIC Data type with fixed precision and scale. This data type is recommended for storing currency values. | - - |
| ||||||||||||||||||||
DOUBLE A floating point number. Should not be used to represent currency values, because of rounding problems. | - - |
| ||||||||||||||||||||
FLOAT A floating point number. Should not be used to represent currency values, because of rounding problems. | - - |
| ||||||||||||||||||||
FLOAT8 A floating point number. Should not be used to represent currency values, because of rounding problems. | - - |
| ||||||||||||||||||||
REAL A single precision floating point number. Should not be used to represent currency values, because of rounding problems. | -
|
| ||||||||||||||||||||
FLOAT4 A single precision floating point number. Should not be used to represent currency values, because of rounding problems. | -
|
| ||||||||||||||||||||
TIME The time data type. The format is hh:mm:ss. | - - |
| ||||||||||||||||||||
DATE The date data type. The format is yyyy- | - - |
| ||||||||||||||||||||
TIMESTAMP The timestamp data type. The format is yyyy- | - - |
| ||||||||||||||||||||
DATETIME The timestamp data type. The format is yyyy- | - - |
| ||||||||||||||||||||
SMALLDATETIME The timestamp data type. The format is yyyy- | - - |
| ||||||||||||||||||||
BINARY Represents a byte array. For very long arrays, use The maximum size is 2 GB, but the whole object is kept in memory when using this data type. The precision is a size constraint; only the actual data is persisted. For large text data | - - |
| ||||||||||||||||||||
VARBINARY Represents a byte array. For very long arrays, use The maximum size is 2 GB, but the whole object is kept in memory when using this data type. The precision is a size constraint; only the actual data is persisted. For large text data | - - |
| ||||||||||||||||||||
LONGVARBINARY Represents a byte array. For very long arrays, use The maximum size is 2 GB, but the whole object is kept in memory when using this data type. The precision is a size constraint; only the actual data is persisted. For large text data | - - |
| ||||||||||||||||||||
RAW Represents a byte array. For very long arrays, use The maximum size is 2 GB, but the whole object is kept in memory when using this data type. The precision is a size constraint; only the actual data is persisted. For large text data | - - |
| ||||||||||||||||||||
BYTEA Represents a byte array. For very long arrays, use The maximum size is 2 GB, but the whole object is kept in memory when using this data type. The precision is a size constraint; only the actual data is persisted. For large text data | - - |
| ||||||||||||||||||||
VARCHAR A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
LONGVARCHAR A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
VARCHAR2 A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
NVARCHAR A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
NVARCHAR2 A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
VARCHARCASESENSITIVE A Unicode String. Use two single quotes ('') to create a quote.The maximum precision is
only the actual data is persisted. The whole text is loaded into memory when using this data type. For large text data see there for details. | - - |
| ||||||||||||||||||||
VARCHARIGNORECASE Same as Stored in mixed case.The maximum precision is
the actual data is persisted.The whole text is loaded into memory when using this data type. For large text data | - - |
| ||||||||||||||||||||
BLOB Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB and Advanced / Large Objects. |
|
| ||||||||||||||||||||
TINYBLOB Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB and Advanced / Large Objects. |
|
| ||||||||||||||||||||
MEDIUMBLOB Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB |
and Advanced / Large Objects. |
|
| ||||||||||||||||||||
LONGBLOB Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB |
and Advanced / Large Objects. |
|
| ||||||||||||||||||||
IMAGE Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB |
and Advanced / Large Objects. |
|
| ||||||||||||||||||||
OID Like BINARY, but intended for very large values such as files or images. Unlike when using BINARY, large objects are notkept fully in-memory. Use PreparedStatement.setBinaryStream to store values.See also CLOB and Advanced / Large Objects. |
|
| ||||||||||||||||||||
CLOB CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
TINYTEXT CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
TEXT CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
MEDIUMTEXT CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
LONGTEXT CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
NTEXT CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
| ||||||||||||||||||||
NCLOB CLOB is like VARCHAR, but intended for very large values. Unlike when using VARCHAR, large CLOB objects are not kept fully in-memory; instead, they are streamed. CLOB should be used for documents and texts with arbitrary size such as XML or HTML documents, text files, or memo fields of unlimited size. Use PreparedStatment.setCharacterStream to store values. VARCHAR should be used for text with relatively short average size (for example shorter than 200 characters). Short CLOB values are stored inline, but there is an overhead compared to VARCHAR. |
|
|