Skip to main content

Struct

Conceptually, a STRUCT column contains an ordered list of columns called “entries”. The entries are referenced by name using strings. This document refers to those entry names as keys. Each row in the STRUCT column must have the same keys. The names of the struct entries are part of the schema. Each row in a STRUCT column must have the same layout. The names of the struct entries are case-insensitive.

STRUCTs are typically used to nest multiple columns into a single column, and the nested column can be of any type, including other STRUCTs and LISTs.

STRUCTs are similar to PostgreSQL's ROW type. The key difference is that SereneDB STRUCTs require the same keys in each row of a STRUCT column. This allows SereneDB to provide significantly improved performance by fully utilizing its vectorized execution engine, and also enforces type consistency for improved correctness. SereneDB includes a row function as a special way to produce a STRUCT, but does not have a ROW data type. See an example below and the STRUCT functions documentation for details.

See the data types overview for a comparison between nested data types.

Creating Structs

Structs can be created using the struct_pack(name := expr, ...) function, the equivalent array notation {'name': expr, ...}, using a row variable, or using the row function.

Create a struct using the struct_pack function. Note the lack of single quotes around the keys and the use of the := operator:

Query
SELECT struct_pack(key1 := 'value1', key2 := 42) AS s;
Result
 s------------- (value1,42)

Create a struct using the array notation:

Query
SELECT {'key1': 'value1', 'key2': 42} AS s;
Result
 s------------- (value1,42)

Create a struct using a row variable:

Query
SELECT d AS s FROM (SELECT 'value1' AS key1, 42 AS key2) d;
Result
 s------------- (value1,42)

Create a struct of integers:

Query
SELECT {'x': 1, 'y': 2, 'z': 3} AS s;
Result
 s--------- (1,2,3)

Create a struct of strings with a NULL value:

Query
SELECT {'yes': 'alpha', 'maybe': 'beta', 'huh': NULL, 'no': 'gamma'} AS s;
Result
 s--------------------- (alpha,beta,,gamma)

Create a struct with a different type for each key:

Query
SELECT {'key1': 'string', 'key2': 1, 'key3': 12.345} AS s;
Result
 s------------------- (string,1,12.345)

Create a struct of structs with NULL values:

Query
SELECT {        'birds': {'yes': 'duck', 'maybe': 'goose', 'huh': NULL, 'no': 'heron'},        'aliens': NULL,        'amphibians': {'yes': 'frog', 'maybe': 'salamander', 'huh': 'dragon', 'no': 'toad'}    } AS s;
Result
 s---------------------------------------------------------- ("(duck,goose,,heron)",,"(frog,salamander,dragon,toad)")

Adding or Updating Fields of Structs

To add new fields or update existing ones, you can use struct_update:

Query
SELECT struct_update({'a': 1, 'b': 2}, b := 3, c := 4) AS s;
Result
 s--------- (1,3,4)

Alternatively, struct_insert also allows adding new fields but not updating existing ones.

Retrieving from Structs

Retrieving a value from a struct can be accomplished using dot notation, bracket notation, or through struct functions like struct_extract.

Use dot notation to retrieve the value at a key's location. In the following query, the subquery generates a struct column a, which we then query with a.x.

Query
SELECT a.x FROM (SELECT {'x': 1, 'y': 2, 'z': 3} AS a);
Result
 x--- 1

If a key contains a space, simply wrap it in double quotes (").

Query
SELECT a."x space" FROM (SELECT {'x space': 1, 'y': 2, 'z': 3} AS a);
Result
 x space---------       1

Bracket notation may also be used. Note that this uses single quotes (') since the goal is to specify a certain string key and only constant expressions may be used inside the brackets (no expressions):

Query
SELECT a['x space'] FROM (SELECT {'x space': 1, 'y': 2, 'z': 3} AS a);
Result
 a--- 1

The struct_extract function is also equivalent. This returns 1:

Query
SELECT struct_extract({'x space': 1, 'y': 2, 'z': 3}, 'x space');
Result
 struct_extract----------------              1

unnest / STRUCT.*

Rather than retrieving a single key from a struct, the unnest special function can be used to retrieve all keys from a struct as separate columns. This is particularly useful when a prior operation creates a struct of unknown shape, or if a query must handle any potential struct keys:

Query
SELECT unnest(a)FROM (SELECT {'x': 1, 'y': 2, 'z': 3} AS a);
Result
 x | y | z---+---+--- 1 | 2 | 3

The same can be achieved with the star notation (*), which additionally allows modifications of the returned columns:

Query
SELECT a.* EXCLUDE ('y')FROM (SELECT {'x': 1, 'y': 2, 'z': 3} AS a);
Result
 x | z---+--- 1 | 3

Dot Notation Order of Operations

Referring to structs with dot notation can be ambiguous with referring to schemas and tables. In general, SereneDB looks for columns first, then for struct keys within columns. SereneDB resolves references in these orders, using the first match to occur:

No Dots

Query
SELECT part1FROM tbl;
Result
 part1---------- ("(42)")
  1. part1 is a column

One Dot

Query
SELECT part1.part2FROM tbl;
Result
 part2------- (42)
  1. part1 is a table, part2 is a column
  2. part1 is a column, part2 is a property of that column

Two (or More) Dots

Query
SELECT part1.part2.part3FROM tbl;
Result
 part3-------    42
  1. part1 is a schema, part2 is a table, part3 is a column
  2. part1 is a table, part2 is a column, part3 is a property of that column
  3. part1 is a column, part2 is a property of that column, part3 is a property of that column

Any extra parts (e.g., .part4.part5, etc.) are always treated as properties

Creating Structs with the row Function

The row function can be used to automatically convert multiple columns to a single struct column. When using row the keys will be empty strings allowing for easy insertion into a table with a struct column. Columns, however, cannot be initialized with the row function, and must be explicitly named. For example, inserting values into a struct column using the row function:

Query
CREATE TABLE t1 (s STRUCT(v VARCHAR, i INTEGER));
INSERT INTO t1 VALUES (row('a', 42));

The table will contain a single entry:

Query
SELECT * FROM t1;
Result
 s-------- (a,42)

The following produces the same result as above:

Query
CREATE TABLE t1 AS (    SELECT row('a', 42)::STRUCT(v VARCHAR, i INTEGER));

Initializing a struct column with the row function will fail:

Query
CREATE TABLE t2 AS SELECT row('a');
Result
db error: ERROR: A table cannot be created from an unnamed struct

When casting between structs, the names of at least one field have to match. Therefore, the following query will fail:

Query
SELECT a::STRUCT(y INTEGER) AS bFROM    (SELECT {'x': 42} AS a);
Result
db error: ERROR: STRUCT to STRUCT cast must have at least one matching member

A workaround for this is to use struct_pack instead:

Query
SELECT struct_pack(y := a.x) AS bFROM    (SELECT {'x': 42} AS a);
Result
 b------ (42)

The row function can be used to return unnamed structs. For example:

Query
SELECT row(x, x + 1, y) FROM (SELECT 1 AS x, 'a' AS y) AS s;
Result
 row--------- (1,2,a)

This produces (1, 2, a).

If using multiple expressions when creating a struct, the row function is optional. The following query returns the same result as the previous one:

Query
SELECT (x, x + 1, y) AS s FROM (SELECT 1 AS x, 'a' AS y);
Result
 s--------- (1,2,a)

Comparison and Ordering

The STRUCT type can be compared using all the comparison operators. These comparisons can be used in logical expressions such as WHERE and HAVING clauses and return BOOLEAN values.

Comparisons are done in lexicographical order, with individual entries being compared as usual except that NULL values are treated as larger than all other values.

Specifically:

  • If all values of s1 and s2 compare equal, then s1 and s2 compare equal.
  • else, if s1.value[i] < s2.value[i] OR s2.value[i] is NULL for the first index i where s1.value[i] != s2.value[i], then s1 is less than s2, and vice versa.

Structs of different types are implicitly cast to a struct type with the union of the involved keys, following the rules for combination casting.

The following queries return true:

Query
SELECT {'k1': 0, 'k2': 0} < {'k1': 1, 'k2': 0};
Result
 ?column?---------- t
Query
SELECT {'k1': 'hello'} < {'k1': 'world'};
Result
 ?column?---------- t
Query
SELECT {'k1': 0, 'k2': 0} < {'k1': 0, 'k2': NULL};
Result
 ?column?---------- t
Query
SELECT {'k1': 0} < {'k2': 0};
Result
 ?column?---------- t
Query
SELECT  {'k1': 0, 'k2': 0} < {'k2': 0, 'k3': 0};
Result
 ?column?---------- t
Query
SELECT {'k1': 1, 'k2': 0} > {'k3': 0, 'k1': 0};
Result
 ?column?---------- t
Query
SELECT {'k1': [0]} < {'k1': [0, 0]};
Result
 ?column?---------- t
Query
SELECT {'k1': 0, 'k2': 0} < {'k3': 0, 'k1': 1};
Result
 ?column?---------- t

The following queries return false:

Query
SELECT {'k1': 1, 'k2': 0} < {'k1': 0, 'k2': 1};
Result
 ?column?---------- f
Query
SELECT {'k1': 1} > {'k2': 0};
Result
 ?column?---------- f
Query
SELECT  {'k1': 1, 'k2': 0} > {'k2': 0, 'k3': 0};
Result
 ?column?---------- f

Updating the Schema

With SereneDB it's possible to update the sub-schema of structs using the ALTER TABLE clause. Adding, dropping or renaming a struct field rewrites the stored values of the column; added fields are backfilled with NULL. Nested structs are addressed with a dotted path (s.sub.field).

To follow the examples, initialize the test table as follows:

Query
CREATE TABLE test (s STRUCT(i INTEGER, j INTEGER));
INSERT INTO test VALUES (ROW(1, 1)), (ROW(2, 2));

Adding a Field

Add field k INTEGER to struct s in table test:

Query
ALTER TABLE test ADD COLUMN s.k INTEGER;
FROM test;
Result
 s-------- (1,1,) (2,2,)

Dropping a Field

Drop field i from struct s in table test:

Query
ALTER TABLE test DROP COLUMN s.i;
FROM test;
Result
 s------ (1,) (2,)

Renaming a Field

Rename field j of struct s to v1 in table test:

Query
ALTER TABLE test RENAME COLUMN s.j TO v1;
FROM test;
Result
 s------ (1,) (2,)

Functions

See Struct Functions.