Appendix F. VoltDB Datatype Compatibility

Documentation

VoltDB Home » Documentation » Using VoltDB
< previoustable of contentsnext >

Appendix F. VoltDB Datatype Compatibility

VoltDB supports nine datatypes. When invoking stored procedures from different programming languages or queuing SQL statements within a Java stored procedure, you must use an appropriate language-specific value and datatype for arguments corresponding to placeholders in the query. This appendix provides the mapping of language-specific datatypes to the corresponding VoltDB datatype.

In several cases, there are multiple possible language-specific datatypes that can be used. The following tables highlight the best possible matches in bold.

F.1. Java and VoltDB Datatype Compatibility

Table F.1, “Java and VoltDB Datatype Compatibility” shows the compatible Java datatypes for each VoltDB datatype when:

  • Queuing SQL statements using the voltdbQueueSql method

  • Calling simple stored procedures defined using the CREATE PROCEDURE AS statement

  • Calling default stored procedures created for each table in the schema

Note that when calling user-defined stored procedures written in Java, you can use additional datatypes, including arrays and the VoltTable object, as arguments to the stored procedure, as long as the actual query invocations within the stored procedure use the following datatypes. Another important distinction to be aware of is that VoltDB only accepts primitive numeric types (byte, short, int, and so on) and not their reference type equivalents (Byte, Short, Integer, etc.).

Table F.1. Java and VoltDB Datatype Compatibility

SQL DatatypeCompatible Java DatatypesNotes
TINYINT

byte
short
int
long
String

Larger datatypes (short, int, and long) are valid input types. However, VoltDB throws a runtime error if the value exceeds the allowable range of a TINYINT.

String input must be a properly formatted text representation of an integer value in the correct range.

SMALLINT

byte
short
int
long
String

Larger datatypes (int and long) are valid input types. However, VoltDB throws a runtime error if the value exceeds the allowable range of a SMALLINT.

String input must be a properly formatted text representation of an integer value in the correct range.

INTEGER

byte
short
int
long
String

A larger datatype (long) is a valid input type. However, VoltDB throws a runtime error if the value exceeds the allowable range of an INTEGER.

String input must be a properly formatted text representation of an integer value in the correct range.

BIGINT

byte
short
int
long
String

String input must be a properly formatted text representation of an integer value in the correct range.

FLOAT

double
float
byte
short
int
long
String

String input must be a properly formatted text representation of a floating point value.

DECIMAL

BigDecimal
double
float
byte
short
int
long
String

String input must be a properly formatted text representation of a decimal number.

VARCHAR()

String
byte[]
byte
short
int
long
float
double
BigDecimal
VoltDB TimestampType

Byte arrays are interpreted as UTF-8 encoded string values. String objects can use other encodings.

Numeric and timestamp values are converted to their string representation. For example, the double value 13.25 is interpreted as "13.25" when converted to a VARCHAR.

VARBINARY()

String
byte[]

String input is interpreted as a hex-encoded binary value.
TIMESTAMP

VoltDB TimestampType
int
long
String

For String variables, the text must be formatted as either YYYY-MM-DD hh.mm.ss.nnnnnn or just the date portion YYYY-MM-DD.

< previoustable of contentsnext >