Connections automatically convert query results to appropriate Racket types. Likewise, query parameters are accepted as Racket values and converted to the appropriate SQL type.
If a query result contains a column with a SQL type not supported by this library, an exception is raised. As a workaround, cast the column to a supported type:
The exception for unsupported types in result columns is raised when the query is executed, not when it is prepared; for parameters it is raised when the parameter values are supplied. Thus even unexecutable prepared statements can be inspected using prepared-statement-parameter-types and prepared-statement-result-types.
This section describes the correspondences between SQL types and Racket types for the supported database systems.
This section applies to connections created with postgresql-connect.
The following table lists the PostgreSQL types known to this library, along with their corresponding Racket representations.
The 'char1 type, written "char" in PostgreSQL’s SQL syntax (the quotation marks are significant), is one byte, essentially a tiny integer written as a character.
A SQL value of type decimal is converted to either an exact rational or +nan.0. When converting Racket values to SQL decimal, exact rational values representable by finite decimal strings are converted without loss of precision. (Precision may be lost, of course, if the value is then stored in a database field of lower precision.) Other real values are converted to decimals with a loss of precision. In PostgreSQL, numeric and decimal refer to the same type.
PostgreSQL user-defined domains are supported in query results if the underlying type is supported. Recordset headers and prepared-statement-result-types report them in terms of the underlying type. Parameters with user-defined domain types are not currently supported. As a workaround, cast the parameter to the underlying type. For example, if the type of $1 is a domain whose underlying type is integer, then replace $1 with ($1::integer).
For each type in the table above, the corresponding array type is also supported, using the pg-array structure. Use the = ANY syntax with an array parameter instead of dynamically constructing a SQL IN expression:
A list may be provided for an array parameter, in which case it is automatically converted using list->pg-array. The type annotation can be dropped when the array type can be inferred from the left-hand side.
PostgreSQL defines many other types, such as network addresses and row types. These are currently not supported, but support may be added in future versions of this library.
This section applies to connections created with mysql-connect.
The following table lists the MySQL types known to this library, along with their corresponding Racket representations.
MySQL does not report specific parameter types for prepared queries,
instead assigning them the type var-string. Consequently,
conversion of Racket values to var-string parameters accepts
strings, numbers (rational?—
The MySQL time type represents time intervals, which may not correspond to times of day (for example, the interval may be negative or larger than 24 hours). In conversion from MySQL results to Racket values, those time values that represent times of day are converted to sql-time values; the rest are represented by sql-interval values.
The MySQL enum and set types are not supported. As a workaround, cast them to/from either integers or strings.
This section applies to connections created with sqlite3-connect.
The following table lists the SQLite types known to this library, along with their corresponding Racket representations.
Unlike PostgreSQL and MySQL, SQLite does not enforce declared type constraints (with the exception of integer primary key) on columns. Rather, every SQLite value has an associated “storage class”.
SQLite storage class
SQLite does not report specific parameter and result types for prepared queries. Instead, they are assigned the pseudotype 'any. Conversion of Racket values to parameters accepts strings, bytes, and real numbers.
An exact integer that cannot be represented as a 64-bit signed integer is converted as real, not integer.
The following table lists the ODBC types known to this library, along with their corresponding Racket representations.
Not all ODBC drivers provide specific parameter type information for
prepared queries. Some omit parameter type information entirely or,
worse, assign all parameters a single type such as varchar. To
avoid enforcing irrelevant type constraints in the last case,
connections only attempt to fetch and enforce parameter types when the
connection is made using the #:strict-parameter-type?
option. Otherwise, the connection assigns all parameters the type
'unknown. (The 'unknown type is also used when
specific parameter types are requested but are not available.)
Conversion of Racket values to 'unknown parameters accepts
strings, bytes, numbers (rational?—
The ODBC type 'bit1 represents a single bit, unlike the standard SQL bit(N) type.
Interval types are not currently supported on ODBC.
This section describes data types for representing various SQL types that have no existing appropriate counterpart in Racket.
SQL NULL is translated into the unique sql-null value.
The DATE, TIME (WITH TIME ZONE and without), TIMESTAMP (WITH TIME ZONE and without), and INTERVAL SQL types are represented by the following structures.
See also Datetime Type Utilities for more functions on datetime values.
(struct sql-date (year month day)) year : exact-integer? month : (integer-in 0 12) day : (integer-in 0 31)
Dates with zero-valued month or day components are a MySQL extension.
(struct sql-time (hour minute second nanosecond tz)) hour : exact-nonnegative-integer? minute : exact-nonnegative-integer? second : exact-nonnegative-integer? nanosecond : exact-nonnegative-integer? tz : (or/c exact-integer? #f)
(struct sql-timestamp ( year month day hour minute second nanosecond tz)) year : exact-nonnegative-integer? month : exact-nonnegative-integer? day : exact-nonnegative-integer? hour : exact-nonnegative-integer? minute : exact-nonnegative-integer? second : exact-nonnegative-integer? nanosecond : exact-nonnegative-integer? tz : (or/c exact-integer? #f)
The tz field indicates the time zone offset as the number of seconds east of GMT (as in SRFI 19). If tz is #f, the time or timestamp does not carry time zone information.
The sql-time and sql-timestamp structures store fractional seconds to nanosecond precision for compatibility with SRFI 19. Note, however, that database systems generally do not support nanosecond precision; PostgreSQL, for example, only supports microsecond precision.
(struct sql-interval ( years months days hours minutes seconds nanoseconds)) years : exact-integer? months : exact-integer? days : exact-integer? hours : exact-integer? minutes : exact-integer? seconds : exact-integer? nanoseconds : exact-integer?
That is, an interval consists of two groups of components: year-month and day-time, and normalization is done only within groups. In fact, the SQL standard recognizes those two types of intervals separately (see sql-year-month-interval? and sql-day-time-interval?, below), and does not permit combining them. Intervals such as 1 month 3 days are a PostgreSQL extension.
(sql-interval->sql-time interval [failure]) → any interval : sql-interval? failure : any/c = (lambda () (error ....))
hours, minutes, seconds, and nanoseconds must all be non-negative
hours must be between 0 and 23
If interval is out of range, the failure value is called, if it is a procedure, or returned, otherwise.
The BIT and BIT VARYING (VARBIT) SQL types are represented by sql-bits values.
(sql-bits->list b) → (listof boolean?) b : sql-bits?
(sql-bits->string b) → string? b : sql-bits?
(list->sql-bits lst) → sql-bits? lst : (listof boolean?)
(string->sql-bits s) → sql-bits? s : string?