# Class TypeCode (3.68.0)

3.68.0 (latest) 3.67.0 3.66.0 3.65.0 3.64.0 3.63.0 3.62.0 3.61.0 3.60.0 3.59.0 3.58.0 3.57.0 3.56.0 3.55.0 3.54.0 3.53.0 3.52.0 3.51.0 3.50.1 3.46.0 3.45.0 3.44.0 3.43.0 3.42.0 3.41.0 3.40.1 3.39.0 3.38.0 3.37.0 3.36.0 3.35.1 3.34.0 3.33.0 3.32.0 3.31.0 3.30.0 3.29.0 3.28.0 3.27.1 3.26.0 3.25.0 3.24.0 3.23.0 3.22.2 3.21.0 3.20.0 3.19.0 3.18.0 3.17.0 3.16.0 3.15.1 3.14.1 3.13.0 3.12.1 3.11.1 3.10.0 3.9.0 3.8.0 3.7.0 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0 3.1.0 3.0.0 2.1.1 2.0.0 1.19.3 1.18.0 1.17.1 1.16.0 1.15.1 1.14.0 1.13.0 1.12.0 1.11.0 1.10.0

    TypeCode(value)

`TypeCode` is used as part of `Type][google.spanner.v1.Type]` to
indicate the type of a Cloud Spanner value.

Each legal value of a type can be encoded to or decoded from a JSON
value, using the encodings described below. All Cloud Spanner values
can be `null`, regardless of type; `null`\\ s are always encoded
as a JSON `null`.

        If the schema has the column option
        `allow_commit_timestamp=true`, the placeholder string
        `"spanner.commit_timestamp()"` can be used to instruct the
        system to insert the commit timestamp associated with the
        transaction commit.
    DATE (5):
        Encoded as `string` in RFC 3339 date format.
    STRING (6):
        Encoded as `string`.
    BYTES (7):
        Encoded as a base64-encoded `string`, as described in RFC
        4648, section 4.
    ARRAY (8):
        Encoded as `list`, where the list elements are represented
        according to
        `array_element_type][google.spanner.v1.Type.array_element_type]`.
    STRUCT (9):
        Encoded as `list`, where list element `i` is represented
        according to
        [struct_type.fields[i]][google.spanner.v1.StructType.fields].
    NUMERIC (10):
        Encoded as `string`, in decimal format or scientific
        notation format. Decimal format: `[+-]Digits[.[Digits]]`
        or `[+-][Digits].Digits`

        Scientific notation:
        `[+-]Digits[.[Digits]][ExponentIndicator[+-]Digits]` or
        `[+-][Digits].Digits[ExponentIndicator[+-]Digits]`
        (ExponentIndicator is `"e"` or `"E"`)
    JSON (11):
        Encoded as a JSON-formatted `string` as described in RFC
        7159. The following rules are applied when parsing JSON
        input:

        - Whitespace characters are not preserved.
        - If a JSON object has duplicate keys, only the first key is
          preserved.
        - Members of a JSON object are not guaranteed to have their
          order preserved.
        - JSON array elements will have their order preserved.
    PROTO (13):
        Encoded as a base64-encoded `string`, as described in RFC
        4648, section 4.
    ENUM (14):
        Encoded as `string`, in decimal format.
    INTERVAL (16):
        Encoded as `string`, in `ISO8601` duration format -
        `P[n]Y[n]M[n]DT[n]H[n]M[n[.fraction]]S` where `n` is an
        integer. For example, `P1Y2M3DT4H5M6.5S` represents time
        duration of 1 year, 2 months, 3 days, 4 hours, 5 minutes,
        and 6.5 seconds.
    UUID (17):
        Encoded as `string`, in lower-case hexa-decimal format, as
        described in RFC 9562, section 4.

| ## Enums ||
|---|---|
| **Name** | **Description** |
| `TYPE_CODE_UNSPECIFIED` | Not specified. |
| `BOOL` | Encoded as JSON \`true\` or \`false\`. |
| `INT64` | Encoded as \`string\`, in decimal format. |
| `FLOAT64` | Encoded as \`number\`, or the strings \`"NaN"\`, \`"Infinity"\`, or \`"-Infinity"\`. |
| `FLOAT32` | Encoded as \`number\`, or the strings \`"NaN"\`, \`"Infinity"\`, or \`"-Infinity"\`. |
| `TIMESTAMP` | Encoded as \`string\` in RFC 3339 timestamp format. The time zone must be present, and must be \`"Z"\`. |