text:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<TITLE
>Arrays</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.0.10 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Data Types"
HREF="datatype.html"><LINK
REL="PREVIOUS"
TITLE="XML Type"
HREF="datatype-xml.html"><LINK
REL="NEXT"
TITLE="Composite Types"
HREF="rowtypes.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2012-09-19T22:08:45">

PostgreSQL 9.0.10 Documentation

Prev	Up	Chapter 8. Data Types	Next

8.14. Arrays

  PostgreSQL allows columns of a table to be
  defined as variable-length multidimensional arrays. Arrays of any
  built-in or user-defined base type, enum type, or composite type
  can be created.
  Arrays of domains are not yet supported.

8.14.1. Declaration of Array Types

  To illustrate the use of array types, we create this table:

CREATE TABLE sal_emp (
    name            text,
    pay_by_quarter  integer[],
    schedule        text[][]
);

  As shown, an array data type is named by appending square brackets
  (<TT
CLASS="LITERAL"
>[]</TT
>) to the data type name of the array elements.  The
  above command will create a table named
  <TT
CLASS="STRUCTNAME"
>sal_emp</TT
> with a column of type
  <TT
CLASS="TYPE"
>text</TT
> (<TT
CLASS="STRUCTFIELD"
>name</TT
>), a
  one-dimensional array of type <TT
CLASS="TYPE"
>integer</TT
>
  (<TT
CLASS="STRUCTFIELD"
>pay_by_quarter</TT
>), which represents the
  employee's salary by quarter, and a two-dimensional array of
  <TT
CLASS="TYPE"
>text</TT
> (<TT
CLASS="STRUCTFIELD"
>schedule</TT
>), which
  represents the employee's weekly schedule.

  The syntax for <TT
CLASS="COMMAND"
>CREATE TABLE</TT
> allows the exact size of
  arrays to be specified, for example:

CREATE TABLE tictactoe (
    squares   integer[3][3]
);

  However, the current implementation ignores any supplied array size
  limits, i.e., the behavior is the same as for arrays of unspecified
  length.

  The current implementation does not enforce the declared
  number of dimensions either.  Arrays of a particular element type are
  all considered to be of the same type, regardless of size or number
  of dimensions.  So, declaring the array size or number of dimensions in
  <TT
CLASS="COMMAND"
>CREATE TABLE</TT
> is simply documentation; it does not
  affect run-time behavior.

  An alternative syntax, which conforms to the SQL standard by using
  the keyword <TT
CLASS="LITERAL"
>ARRAY</TT
>, can be used for one-dimensional arrays.
  <TT
CLASS="STRUCTFIELD"
>pay_by_quarter</TT
> could have been defined
  as:

    pay_by_quarter  integer ARRAY[4],

  Or, if no array size is to be specified:

    pay_by_quarter  integer ARRAY,

  As before, however, PostgreSQL does not enforce the
  size restriction in any case.

8.14.2. Array Value Input

   To write an array value as a literal constant, enclose the element
   values within curly braces and separate them by commas.  (If you
   know C, this is not unlike the C syntax for initializing
   structures.)  You can put double quotes around any element value,
   and must do so if it contains commas or curly braces.  (More
   details appear below.)  Thus, the general format of an array
   constant is the following:

'{ <TT
CLASS="REPLACEABLE"
>val1</TT
> <TT
CLASS="REPLACEABLE"
>delim</TT
> <TT
CLASS="REPLACEABLE"
>val2</TT
> <TT
CLASS="REPLACEABLE"
>delim</TT
> ... }'

   where <TT
CLASS="REPLACEABLE"
>delim</TT
> is the delimiter character
   for the type, as recorded in its <TT
CLASS="LITERAL"
>pg_type</TT
> entry.
   Among the standard data types provided in the
   PostgreSQL distribution, all use a comma
   (<TT
CLASS="LITERAL"
>,</TT
>), except for type <TT
CLASS="TYPE"
>box</TT
> which uses a semicolon
   (<TT
CLASS="LITERAL"
>;</TT
>). Each <TT
CLASS="REPLACEABLE"
>val</TT
> is
   either a constant of the array element type, or a subarray. An example
   of an array constant is:

'{{1,2,3},{4,5,6},{7,8,9}}'

   This constant is a two-dimensional, 3-by-3 array consisting of
   three subarrays of integers.

   To set an element of an array constant to NULL, write <TT
CLASS="LITERAL"
>NULL</TT
>
   for the element value.  (Any upper- or lower-case variant of
   <TT
CLASS="LITERAL"
>NULL</TT
> will do.)  If you want an actual string value
   "NULL", you must put double quotes around it.

   (These kinds of array constants are actually only a special case of
   the generic type constants discussed in Section 4.1.2.7.  The constant is initially
   treated as a string and passed to the array input conversion
   routine.  An explicit type specification might be necessary.)

   Now we can show some <TT
CLASS="COMMAND"
>INSERT</TT
> statements:

INSERT INTO sal_emp
    VALUES ('Bill',
    '{10000, 10000, 10000, 10000}',
    '{{"meeting", "lunch"}, {"training", "presentation"}}');

INSERT INTO sal_emp
    VALUES ('Carol',
    '{20000, 25000, 25000, 25000}',
    '{{"breakfast", "consulting"}, {"meeting", "lunch"}}');

  The result of the previous two inserts looks like this:

SELECT * FROM sal_emp;
 name  |      pay_by_quarter       |                 schedule
-------+---------------------------+-------------------------------------------
 Bill  | {10000,10000,10000,10000} | {{meeting,lunch},{training,presentation}}
 Carol | {20000,25000,25000,25000} | {{breakfast,consulting},{meeting,lunch}}
(2 rows)

  Multidimensional arrays must have matching extents for each
  dimension. A mismatch causes an error, for example:

INSERT INTO sal_emp
    VALUES ('Bill',
    '{10000, 10000, 10000, 10000}',
    '{{"meeting", "lunch"}, {"meeting"}}');
ERROR:  multidimensional arrays must have array expressions with matching dimensions

  The <TT
CLASS="LITERAL"
>ARRAY</TT
> constructor syntax can also be used:

INSERT INTO sal_emp
    VALUES ('Bill',
    ARRAY[10000, 10000, 10000, 10000],
    ARRAY[['meeting', 'lunch'], ['training', 'presentation']]);

INSERT INTO sal_emp
    VALUES ('Carol',
    ARRAY[20000, 25000, 25000, 25000],
    ARRAY[['breakfast', 'consulting'], ['meeting', 'lunch']]);

  Notice that the array elements are ordinary SQL constants or
  expressions; for instance, string literals are single quoted, instead of
  double quoted as they would be in an array literal.  The <TT
CLASS="LITERAL"
>ARRAY</TT
>
  constructor syntax is discussed in more detail in
  Section 4.2.11.

8.14.3. Accessing Arrays

  Now, we can run some queries on the table.
  First, we show how to access a single element of an array.
  This query retrieves the names of the employees whose pay changed in
  the second quarter:

SELECT name FROM sal_emp WHERE pay_by_quarter[1] <> pay_by_quarter[2];

 name
-------
 Carol
(1 row)

  The array subscript numbers are written within square brackets.
  By default PostgreSQL uses a
  one-based numbering convention for arrays, that is,
  an array of <TT
CLASS="REPLACEABLE"
>n</TT
> elements starts with <TT
CLASS="LITERAL"
>array[1]</TT
> and
  ends with <TT
CLASS="LITERAL"
>array[<TT
CLASS="REPLACEABLE"
>n</TT
>]</TT
>.

  This query retrieves the third quarter pay of all employees:

SELECT pay_by_quarter[3] FROM sal_emp;

 pay_by_quarter
----------------
          10000
          25000
(2 rows)

  We can also access arbitrary rectangular slices of an array, or
  subarrays.  An array slice is denoted by writing
  <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
>lower-bound</TT
>:<TT
CLASS="REPLACEABLE"
>upper-bound</TT
></TT
>
  for one or more array dimensions.  For example, this query retrieves the first
  item on Bill's schedule for the first two days of the week:

SELECT schedule[1:2][1:1] FROM sal_emp WHERE name = 'Bill';

        schedule
------------------------
 {{meeting},{training}}
(1 row)

  If any dimension is written as a slice, i.e., contains a colon, then all
  dimensions are treated as slices.  Any dimension that has only a single
  number (no colon) is treated as being from <TT
CLASS="LITERAL"
>1</TT
>
  to the number specified.  For example, <TT
CLASS="LITERAL"
>[2]</TT
> is treated as
  <TT
CLASS="LITERAL"
>[1:2]</TT
>, as in this example:

SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';

                 schedule
-------------------------------------------
 {{meeting,lunch},{training,presentation}}
(1 row)

  To avoid confusion with the non-slice case, it's best to use slice syntax
  for all dimensions, e.g., <TT
CLASS="LITERAL"
>[1:2][1:1]</TT
>, not <TT
CLASS="LITERAL"
>[2][1:1]</TT
>.

  An array subscript expression will return null if either the array itself or
  any of the subscript expressions are null.  Also, null is returned if a
  subscript is outside the array bounds (this case does not raise an error).
  For example, if <TT
CLASS="LITERAL"
>schedule</TT
>
  currently has the dimensions <TT
CLASS="LITERAL"
>[1:3][1:2]</TT
> then referencing
  <TT
CLASS="LITERAL"
>schedule[3][3]</TT
> yields NULL.  Similarly, an array reference
  with the wrong number of subscripts yields a null rather than an error.

  An array slice expression likewise yields null if the array itself or
  any of the subscript expressions are null.  However, in other
  cases such as selecting an array slice that
  is completely outside the current array bounds, a slice expression
  yields an empty (zero-dimensional) array instead of null.  (This
  does not match non-slice behavior and is done for historical reasons.)
  If the requested slice partially overlaps the array bounds, then it
  is silently reduced to just the overlapping region instead of
  returning null.

  The current dimensions of any array value can be retrieved with the
  array_dims function:

SELECT array_dims(schedule) FROM sal_emp WHERE name = 'Carol';

 array_dims
------------
 [1:2][1:2]
(1 row)

  array_dims produces a <TT
CLASS="TYPE"
>text</TT
> result,
  which is convenient for people to read but perhaps inconvenient
  for programs.  Dimensions can also be retrieved with
  array_upper and array_lower,
  which return the upper and lower bound of a
  specified array dimension, respectively:

SELECT array_upper(schedule, 1) FROM sal_emp WHERE name = 'Carol';

 array_upper
-------------
           2
(1 row)

 array_length will return the length of a specified
 array dimension:

SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';

 array_length
--------------
            2
(1 row)

8.14.4. Modifying Arrays

  An array value can be replaced completely:

UPDATE sal_emp SET pay_by_quarter = '{25000,25000,27000,27000}'
    WHERE name = 'Carol';

  or using the <TT
CLASS="LITERAL"
>ARRAY</TT
> expression syntax:

UPDATE sal_emp SET pay_by_quarter = ARRAY[25000,25000,27000,27000]
    WHERE name = 'Carol';

  An array can also be updated at a single element:

UPDATE sal_emp SET pay_by_quarter[4] = 15000
    WHERE name = 'Bill';

  or updated in a slice:

UPDATE sal_emp SET pay_by_quarter[1:2] = '{27000,27000}'
    WHERE name = 'Carol';

  A stored array value can be enlarged by assigning to elements not already
  present.  Any positions between those previously present and the newly
  assigned elements will be filled with nulls.  For example, if array
  <TT
CLASS="LITERAL"
>myarray</TT
> currently has 4 elements, it will have six
  elements after an update that assigns to <TT
CLASS="LITERAL"
>myarray[6]</TT
>;
  <TT
CLASS="LITERAL"
>myarray[5]</TT
> will contain null.
  Currently, enlargement in this fashion is only allowed for one-dimensional
  arrays, not multidimensional arrays.

  Subscripted assignment allows creation of arrays that do not use one-based
  subscripts.  For example one might assign to <TT
CLASS="LITERAL"
>myarray[-2:7]</TT
> to
  create an array with subscript values from -2 to 7.

  New array values can also be constructed using the concatenation operator,
  <TT
CLASS="LITERAL"
>||</TT
>:

SELECT ARRAY[1,2] || ARRAY[3,4];
 ?column?
-----------
 {1,2,3,4}
(1 row)

SELECT ARRAY[5,6] || ARRAY[[1,2],[3,4]];
      ?column?
---------------------
 {{5,6},{1,2},{3,4}}
(1 row)

  The concatenation operator allows a single element to be pushed onto the
  beginning or end of a one-dimensional array. It also accepts two
  <TT
CLASS="REPLACEABLE"
>N</TT
>-dimensional arrays, or an <TT
CLASS="REPLACEABLE"
>N</TT
>-dimensional
  and an <TT
CLASS="REPLACEABLE"
>N+1</TT
>-dimensional array.

  When a single element is pushed onto either the beginning or end of a
  one-dimensional array, the result is an array with the same lower bound
  subscript as the array operand. For example:

SELECT array_dims(1 || '[0:1]={2,3}'::int[]);
 array_dims
------------
 [0:2]
(1 row)

SELECT array_dims(ARRAY[1,2] || 3);
 array_dims
------------
 [1:3]
(1 row)

  When two arrays with an equal number of dimensions are concatenated, the
  result retains the lower bound subscript of the left-hand operand's outer
  dimension. The result is an array comprising every element of the left-hand
  operand followed by every element of the right-hand operand. For example:

SELECT array_dims(ARRAY[1,2] || ARRAY[3,4,5]);
 array_dims
------------
 [1:5]
(1 row)

SELECT array_dims(ARRAY[[1,2],[3,4]] || ARRAY[[5,6],[7,8],[9,0]]);
 array_dims
------------
 [1:5][1:2]
(1 row)

  When an <TT
CLASS="REPLACEABLE"
>N</TT
>-dimensional array is pushed onto the beginning
  or end of an <TT
CLASS="REPLACEABLE"
>N+1</TT
>-dimensional array, the result is
  analogous to the element-array case above. Each <TT
CLASS="REPLACEABLE"
>N</TT
>-dimensional
  sub-array is essentially an element of the <TT
CLASS="REPLACEABLE"
>N+1</TT
>-dimensional
  array's outer dimension. For example:

SELECT array_dims(ARRAY[1,2] || ARRAY[[3,4],[5,6]]);
 array_dims
------------
 [1:3][1:2]
(1 row)

  An array can also be constructed by using the functions
  array_prepend, array_append,
  or array_cat. The first two only support one-dimensional
  arrays, but array_cat supports multidimensional arrays.

  Note that the concatenation operator discussed above is preferred over
  direct use of these functions. In fact, these functions primarily exist for use
  in implementing the concatenation operator. However, they might be directly
  useful in the creation of user-defined aggregates. Some examples:

SELECT array_prepend(1, ARRAY[2,3]);
 array_prepend
---------------
 {1,2,3}
(1 row)

SELECT array_append(ARRAY[1,2], 3);
 array_append
--------------
 {1,2,3}
(1 row)

SELECT array_cat(ARRAY[1,2], ARRAY[3,4]);
 array_cat
-----------
 {1,2,3,4}
(1 row)

SELECT array_cat(ARRAY[[1,2],[3,4]], ARRAY[5,6]);
      array_cat
---------------------
 {{1,2},{3,4},{5,6}}
(1 row)

SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
      array_cat
---------------------
 {{5,6},{1,2},{3,4}}

8.14.5. Searching in Arrays

  To search for a value in an array, each value must be checked.
  This can be done manually, if you know the size of the array.
  For example:

SELECT * FROM sal_emp WHERE pay_by_quarter[1] = 10000 OR
                            pay_by_quarter[2] = 10000 OR
                            pay_by_quarter[3] = 10000 OR
                            pay_by_quarter[4] = 10000;

  However, this quickly becomes tedious for large arrays, and is not
  helpful if the size of the array is unknown. An alternative method is
  described in Section 9.21. The above
  query could be replaced by:

SELECT * FROM sal_emp WHERE 10000 = ANY (pay_by_quarter);

  In addition, you can find rows where the array has all values
  equal to 10000 with:

SELECT * FROM sal_emp WHERE 10000 = ALL (pay_by_quarter);

  Alternatively, the generate_subscripts function can be used.
  For example:

SELECT * FROM
   (SELECT pay_by_quarter,
           generate_subscripts(pay_by_quarter, 1) AS s
      FROM sal_emp) AS foo
 WHERE pay_by_quarter[s] = 10000;

  This function is described in Table 9-46.

Tip:    Arrays are not sets; searching for specific array elements
   can be a sign of database misdesign.  Consider
   using a separate table with a row for each item that would be an
   array element.  This will be easier to search, and is likely to
   scale better for a large number of elements.

8.14.6. Array Input and Output Syntax

   The external text representation of an array value consists of items that
   are interpreted according to the I/O conversion rules for the array's
   element type, plus decoration that indicates the array structure.
   The decoration consists of curly braces (<TT
CLASS="LITERAL"
>{</TT
> and <TT
CLASS="LITERAL"
>}</TT
>)
   around the array value plus delimiter characters between adjacent items.
   The delimiter character is usually a comma (<TT
CLASS="LITERAL"
>,</TT
>) but can be
   something else: it is determined by the <TT
CLASS="LITERAL"
>typdelim</TT
> setting
   for the array's element type.  Among the standard data types provided
   in the PostgreSQL distribution, all use a comma,
   except for type <TT
CLASS="TYPE"
>box</TT
>, which uses a semicolon (<TT
CLASS="LITERAL"
>;</TT
>).
   In a multidimensional array, each dimension (row, plane,
   cube, etc.) gets its own level of curly braces, and delimiters
   must be written between adjacent curly-braced entities of the same level.

   The array output routine will put double quotes around element values
   if they are empty strings, contain curly braces, delimiter characters,
   double quotes, backslashes, or white space, or match the word
   <TT
CLASS="LITERAL"
>NULL</TT
>.  Double quotes and backslashes
   embedded in element values will be backslash-escaped.  For numeric
   data types it is safe to assume that double quotes will never appear, but
   for textual data types one should be prepared to cope with either the presence
   or absence of quotes.

   By default, the lower bound index value of an array's dimensions is
   set to one.  To represent arrays with other lower bounds, the array
   subscript ranges can be specified explicitly before writing the
   array contents.
   This decoration consists of square brackets (<TT
CLASS="LITERAL"
>[]</TT
>)
   around each array dimension's lower and upper bounds, with
   a colon (<TT
CLASS="LITERAL"
>:</TT
>) delimiter character in between. The
   array dimension decoration is followed by an equal sign (<TT
CLASS="LITERAL"
>=</TT
>).
   For example:

SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
 FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;

 e1 | e2
----+----
  1 |  6
(1 row)

   The array output routine will include explicit dimensions in its result
   only when there are one or more lower bounds different from one.

   If the value written for an element is <TT
CLASS="LITERAL"
>NULL</TT
> (in any case
   variant), the element is taken to be NULL.  The presence of any quotes
   or backslashes disables this and allows the literal string value
   "NULL" to be entered.  Also, for backwards compatibility with
   pre-8.2 versions of PostgreSQL, the array_nulls configuration parameter can be turned
   <TT
CLASS="LITERAL"
>off</TT
> to suppress recognition of <TT
CLASS="LITERAL"
>NULL</TT
> as a NULL.

   As shown previously, when writing an array value you can use double
   quotes around any individual array element. You must do so
   if the element value would otherwise confuse the array-value parser.
   For example, elements containing curly braces, commas (or the data type's
   delimiter character), double quotes, backslashes, or leading or trailing
   whitespace must be double-quoted.  Empty strings and strings matching the
   word <TT
CLASS="LITERAL"
>NULL</TT
> must be quoted, too.  To put a double quote or
   backslash in a quoted array element value, use escape string syntax
   and precede it with a backslash. Alternatively, you can avoid quotes and use
   backslash-escaping to protect all data characters that would otherwise
   be taken as array syntax.

   You can add whitespace before a left brace or after a right
   brace. You can also add whitespace before or after any individual item
   string. In all of these cases the whitespace will be ignored. However,
   whitespace within double-quoted elements, or surrounded on both sides by
   non-whitespace characters of an element, is not ignored.

Note:    Remember that what you write in an SQL command will first be interpreted
   as a string literal, and then as an array.  This doubles the number of
   backslashes you need.  For example, to insert a <TT
CLASS="TYPE"
>text</TT
> array
   value containing a backslash and a double quote, you'd need to write:

INSERT ... VALUES (E'{"\\\\","\\""}');

   The escape string processor removes one level of backslashes, so that
   what arrives at the array-value parser looks like <TT
CLASS="LITERAL"
>{"\\","\""}</TT
>.
   In turn, the strings fed to the <TT
CLASS="TYPE"
>text</TT
> data type's input routine
   become <TT
CLASS="LITERAL"
>\</TT
> and <TT
CLASS="LITERAL"
>"</TT
> respectively.  (If we were working
   with a data type whose input routine also treated backslashes specially,
   <TT
CLASS="TYPE"
>bytea</TT
> for example, we might need as many as eight backslashes
   in the command to get one backslash into the stored array element.)
   Dollar quoting (see Section 4.1.2.4) can be
   used to avoid the need to double backslashes.

Tip:    The <TT
CLASS="LITERAL"
>ARRAY</TT
> constructor syntax (see
   Section 4.2.11) is often easier to work
   with than the array-literal syntax when writing array values in SQL
   commands. In <TT
CLASS="LITERAL"
>ARRAY</TT
>, individual element values are written the
   same way they would be written when not members of an array.

Prev	Home	Next

<ACRONYM
CLASS="ACRONYM"
>XML</ACRONYM
> Type	Up	Composite Types


text:
.field-repeater {
  padding-top: 5px;
}
.field-repeater ul.field-repeater-items,
.field-repeater li.field-repeater-item {
  padding: 0;
  margin: 0;
  list-style: none;
}
.field-repeater ul.field-repeater-items > li.dragged {
  opacity: .7;
  position: absolute;
  padding-top: 15px;
  padding-right: 15px;
  z-index: 2000;
  background-color: #f9f9f9;
  border: 1px dashed #dbdee0;
}
.field-repeater ul.field-repeater-items > li.dragged .repeater-item-remove {
  opacity: 0;
}
.field-repeater ul.field-repeater-items > li.dragged .repeater-item-collapsed-title {
  top: 5px;
}
.field-repeater ul.field-repeater-items > li.placeholder {
  display: block;
  position: relative;
  height: 25px;
  margin-bottom: 5px;
}
.field-repeater ul.field-repeater-items > li.placeholder:before {
  display: block;
  position: absolute;
  font-family: FontAwesome;
  font-weight: normal;
  font-style: normal;
  text-decoration: inherit;
  -webkit-font-smoothing: antialiased;
  *margin-right: .3em;
  content: "\f054";
  color: #d35714;
  left: -10px;
  top: 8px;
  z-index: 2000;
}
.field-repeater li.field-repeater-item {
  position: relative;
  margin-left: 5px;
  padding-left: 15px;
  border-left: 1px solid #dbdee0;
  min-height: 30px;
}
.field-repeater li.field-repeater-item:before {
  color: #bdc3c7;
  font-family: FontAwesome;
  font-weight: normal;
  font-style: normal;
  text-decoration: inherit;
  -webkit-font-smoothing: antialiased;
  *margin-right: .3em;
  content: "\f111";
  font-size: 8px;
  position: absolute;
  left: -4px;
  top: -2px;
}
.field-repeater li.field-repeater-item.collapsed .field-repeater-form {
  display: none;
}
.field-repeater li.field-repeater-item.collapsed .repeater-item-collapse .repeater-item-collapse-one {
  -webkit-transform: scale(1, -1);
  -ms-transform: scale(1, -1);
  transform: scale(1, -1);
}
.field-repeater li.field-repeater-item.collapsed .repeater-item-collapsed-title {
  display: block;
}
.field-repeater li.field-repeater-item .repeater-item-collapsed-title {
  display: none;
  top: -5px;
  position: absolute;
  font-size: 13px;
}
.field-repeater li.field-repeater-item .field-repeater-form {
  position: relative;
  top: -7px;
}
.field-repeater li.field-repeater-item .field-repeater-form:before,
.field-repeater li.field-repeater-item .field-repeater-form:after {
  content: " ";
  display: table;
}
.field-repeater li.field-repeater-item .field-repeater-form:after {
  clear: both;
}
.field-repeater li.field-repeater-item .repeater-item-handle {
  position: absolute;
  top: -6px;
  left: -10px;
  color: #bdc3c7;
  background: #f9f9f9;
  cursor: move;
  opacity: 0;
  border-radius: 999px;
  -webkit-transition: opacity 0.5s;
  transition: opacity 0.5s;
}
.field-repeater li.field-repeater-item .repeater-item-handle:hover {
  color: #999;
}
.field-repeater li.field-repeater-item .repeater-item-collapse {
  position: absolute;
  top: -9px;
  right: 22px;
  z-index: 90;
}
.field-repeater li.field-repeater-item .repeater-item-collapse a,
.field-repeater li.field-repeater-item .repeater-item-collapse button {
  -webkit-transition: transform 0.3s;
  transition: transform 0.3s;
  color: #bdc3c7;
  line-height: 20px;
  display: block;
  font-size: 12px;
}
.field-repeater li.field-repeater-item .repeater-item-collapse a:hover,
.field-repeater li.field-repeater-item .repeater-item-collapse button:hover,
.field-repeater li.field-repeater-item .repeater-item-collapse a:focus,
.field-repeater li.field-repeater-item .repeater-item-collapse button:focus {
  color: #999;
  text-decoration: none;
}
.field-repeater li.field-repeater-item .repeater-item-remove {
  position: absolute;
  top: -10px;
  right: 0;
  z-index: 90;
}
.field-repeater li.field-repeater-item .repeater-item-collapse,
.field-repeater li.field-repeater-item .repeater-item-handle,
.field-repeater li.field-repeater-item .repeater-item-remove {
  width: 20px;
  height: 20px;
  text-align: center;
}
.field-repeater li.field-repeater-item:hover .repeater-item-collapse,
.field-repeater li.field-repeater-item:active .repeater-item-collapse,
.field-repeater li.field-repeater-item:hover .repeater-item-handle,
.field-repeater li.field-repeater-item:active .repeater-item-handle,
.field-repeater li.field-repeater-item:hover .repeater-item-remove,
.field-repeater li.field-repeater-item:active .repeater-item-remove {
  opacity: 1;
}
.field-repeater .field-repeater-add-item {
  position: relative;
  margin-top: 10px;
  margin-left: 20px;
  border: 2px dotted #e0e0e0;
}
.field-repeater .field-repeater-add-item:before {
  color: #bdc3c7;
  font-family: FontAwesome;
  font-weight: normal;
  font-style: normal;
  text-decoration: inherit;
  -webkit-font-smoothing: antialiased;
  *margin-right: .3em;
  content: "\f067";
  font-size: 16px;
  position: absolute;
  left: -23px;
  top: -11px;
}
.field-repeater .field-repeater-add-item > a {
  color: #bdc3c7;
  text-align: center;
  display: block;
  text-decoration: none;
  padding: 20px 10px;
}
.field-repeater .field-repeater-add-item:hover {
  border: 2px dotted rgba(0, 0, 0, 0.1);
}
.field-repeater .field-repeater-add-item:hover:before {
  color: #999;
}
.field-repeater .field-repeater-add-item:hover > a {
  color: #bdc3c7;
}

redpajama_set_name: RedPajamaGithub