Selecto (Selecto v0.3.8)
Selecto is a query builder for Elixir that uses Postgrex to execute queries. It is designed to be a flexible and powerful tool for building complex SQL queries without writing SQL by hand.
domain-configuration
Domain Configuration
Selecto is configured using a domain map. This map defines the database schema, including tables, columns, and associations. Here is an example of a domain map:
%{
source: %{
source_table: "users",
primary_key: :id,
fields: [:id, :name, :email, :age, :active, :created_at, :updated_at],
redact_fields: [],
columns: %{
id: %{type: :integer},
name: %{type: :string},
email: %{type: :string},
age: %{type: :integer},
active: %{type: :boolean},
created_at: %{type: :utc_datetime},
updated_at: %{type: :utc_datetime}
},
associations: %{
posts: %{
queryable: :posts,
field: :posts,
owner_key: :id,
related_key: :user_id
}
}
},
schemas: %{
posts: %{
source_table: "posts",
primary_key: :id,
fields: [:id, :title, :body, :user_id, :created_at, :updated_at],
redact_fields: [],
columns: %{
id: %{type: :integer},
title: %{type: :string},
body: %{type: :string},
user_id: %{type: :integer},
created_at: %{type: :utc_datetime},
updated_at: %{type: :utc_datetime}
},
associations: %{
tags: %{
queryable: :post_tags,
field: :tags,
owner_key: :id,
related_key: :post_id
}
}
},
post_tags: %{
source_table: "post_tags",
primary_key: :id,
fields: [:id, :name, :post_id],
redact_fields: [],
columns: %{
id: %{type: :integer},
name: %{type: :string},
post_id: %{type: :integer}
}
}
},
name: "User",
default_selected: ["name", "email"],
default_aggregate: [{"id", %{"format" => "count"}}],
required_filters: [{"active", true}],
joins: %{
posts: %{
type: :left,
name: "posts",
parameters: [
{:tag, :name}
],
joins: %{
tags: %{
type: :left,
name: "tags"
}
}
}
},
filters: %{
"active" => %{
name: "Active",
type: "boolean",
default: true
}
}
}
query-execution
Query Execution
Selecto provides two execution patterns for better error handling and control flow:
safe-execution-non-raising
Safe Execution (Non-raising)
Use execute/2 and execute_one/2 for applications that prefer explicit error handling:
# Multiple rows
case Selecto.execute(selecto) do
{:ok, {rows, columns, aliases}} ->
# Process successful results
Enum.map(rows, &process_row/1)
{:error, %Postgrex.Error{} = error} ->
# Handle database errors gracefully
Logger.error("Query failed: #{inspect(error)}")
{:error, :database_error}
end
# Single row (useful for COUNT, aggregate queries, or lookups)
case Selecto.execute_one(selecto) do
{:ok, {row, aliases}} ->
# Process single row
extract_values(row, aliases)
{:error, :no_results} ->
# Handle empty result set
{:error, :not_found}
{:error, :multiple_results} ->
# Handle unexpected multiple rows
{:error, :ambiguous_result}
end
error-types
Error Types
All execution functions return structured Selecto.Error for consistent error handling:
{:error, %Selecto.Error{type: :connection_error}}- Database connection failures{:error, %Selecto.Error{type: :query_error}}- SQL execution errors{:error, %Selecto.Error{type: :no_results}}- execute_one/2 when 0 rows returned{:error, %Selecto.Error{type: :multiple_results}}- execute_one/2 when >1 rows returned{:error, %Selecto.Error{type: :timeout_error}}- Query timeout failures
Link to this section Summary
Functions
Apply tenant scope as required filters.
Add array filtering operations to WHERE clauses.
Add array manipulation operations to select fields.
Add array aggregation operations to select fields.
Get all available fields across all joins and the source table.
Add a simple CASE expression to the select fields.
Add a searched CASE expression to the select fields.
Generate a selecto structure from a domain configuration and database connection.
Raise if tenant scope is required and missing.
Create an EXCEPT set operation between two queries.
Generate and run the query, returning {:ok, result} or {:error, reason}.
Execute a query expecting exactly one row, returning {:ok, row} or {:error, reason}.
Execute a query configured with select_shape/2 and return shaped rows.
Execute a query as a database-backed stream.
Execute a query and return results with metadata including SQL, params, and execution time.
Run EXPLAIN for a query and return plan details.
Run EXPLAIN ANALYZE for a query and return plan details.
Get field suggestions for autocomplete or error recovery.
Add a filter to selecto. Send in a tuple with field name and filter value.
Format SQL output for readability.
Configure Selecto from an Ecto repository and schema.
Add to the Group By clause.
Apply optional highlighting to SQL (:ansi or :markdown).
Infer the SQL type of an expression.
Create an INTERSECT set operation between two queries.
Enable a join from the domain configuration or add a custom join dynamically.
Create a parameterized instance of an existing join.
Join with another Selecto query as a subquery.
Add JSON operations to WHERE clauses for filtering with PostgreSQL JSON/JSONB functionality.
Add JSON operations to ORDER BY clauses for sorting with PostgreSQL JSON/JSONB functionality.
Add JSON operations to SELECT clauses for PostgreSQL JSON/JSONB functionality.
Add a LATERAL join to the query.
Limit the number of rows returned by the query.
Set the offset for the query results.
Add to the Order By clause.
Pivot the query to focus on a different table while preserving existing context.
Append filters explicitly to the post-pivot filter list.
Read post-pivot filters from the query set (set.post_pivot_filters).
Append filters explicitly to the pre-pivot filter list.
Read pre-pivot filters from the query set (set.filtered).
Return query filters from legacy and current filter buckets.
Add a required tenant filter to query state.
Return required filters currently attached to the query.
Enhanced field resolution with disambiguation and error handling.
Add a field to the Select list. Send in one or a list of field names or selectable tuples.
Compile a nested selection shape and attach it to the query.
Add subselect fields to return related data as aggregated arrays.
Read tenant context from query state.
Return whether tenant scope is required for this query.
Generate SQL without executing - useful for debugging and caching.
Get the type category for a given SQL type.
Check if two SQL types are compatible for comparisons or assignments.
Create a UNION set operation between two queries.
Add an UNNEST operation to expand array columns into rows.
Validate tenant scope and return :ok or structured validation error.
Add a window function to the query.
Add a Common Table Expression (CTE) to the query using WITH clause.
Add multiple CTEs to the query in a single operation.
Add a recursive Common Table Expression (CTE) to the query.
Attach tenant context to the query state.
Add a VALUES clause to create an inline table from literal data.
Link to this section Types
@type t() :: Selecto.Types.t()
Link to this section Functions
apply_tenant_scope(selecto, opts \\ [])
Apply tenant scope as required filters.
array_filter(selecto, array_filters, opts \\ [])
Add array filtering operations to WHERE clauses.
Supports array containment, overlap, and equality operations.
parameters
Parameters
selecto- The Selecto instancearray_filters- List of array filter tuples or single filteropts- Additional options
examples
Examples
# Array contains
selecto
|> Selecto.array_filter({:array_contains, "tags", ["featured", "new"]})
# Array overlap (has any of the elements)
selecto
|> Selecto.array_filter({:array_overlap, "categories", ["electronics", "computers"]})
# Array contained by
selecto
|> Selecto.array_filter({:array_contained, "permissions", ["read", "write", "admin"]})
# Multiple filters
selecto
|> Selecto.array_filter([
{:array_contains, "special_features", ["Trailers"]},
{:array_overlap, "languages", ["English", "Spanish"]}
])
array_manipulate(selecto, array_operations, opts \\ [])
Add array manipulation operations to select fields.
Supports array construction, modification, and transformation operations.
parameters
Parameters
selecto- The Selecto instancearray_operations- List of array manipulation operationsopts- Additional options
examples
Examples
# Array append
selecto
|> Selecto.array_manipulate({:array_append, "tags", "new-tag", as: "updated_tags"})
# Array remove
selecto
|> Selecto.array_manipulate({:array_remove, "tags", "deprecated", as: "cleaned_tags"})
# Array to string
selecto
|> Selecto.array_manipulate({:array_to_string, "tags", ", ", as: "tag_string"})
array_select(selecto, array_operations, opts \\ [])
Add array aggregation operations to select fields.
Supports ARRAY_AGG, STRING_AGG, and other array aggregation functions with optional DISTINCT, ORDER BY, and filtering.
parameters
Parameters
selecto- The Selecto instancearray_operations- List of array operation tuples or single operationopts- Additional options
examples
Examples
# Simple array aggregation
selecto
|> Selecto.array_select({:array_agg, "film.title", as: "film_titles"})
# Array aggregation with DISTINCT and ORDER BY
selecto
|> Selecto.array_select({:array_agg, "actor.name",
distinct: true,
order_by: [{"actor.last_name", :asc}],
as: "unique_actors"})
# String aggregation with custom delimiter
selecto
|> Selecto.array_select({:string_agg, "tag.name",
delimiter: ", ",
as: "tag_list"})
# Array length operation
selecto
|> Selecto.array_select({:array_length, "tags", 1, as: "tag_count"})
available_fields(selecto)
Get all available fields across all joins and the source table.
case_select(selecto, column, when_clauses, opts \\ [])
Add a simple CASE expression to the select fields.
Simple CASE expressions test a column against specific values and return corresponding results. This is useful for data transformation and categorization.
parameters
Parameters
selecto- The Selecto instancecolumn- Column to test againstwhen_clauses- List of {value, result} tuples for WHEN conditionsopts- Options including :else and :as
examples
Examples
# Simple CASE for film ratings
selecto
|> Selecto.case_select("film.rating", [
{"G", "General Audience"},
{"PG", "Parental Guidance"},
{"PG-13", "Parents Strongly Cautioned"},
{"R", "Restricted"}
], else: "Not Rated", as: "rating_description")
|> Selecto.select(["film.title", "rating_description"])
# Generated SQL:
# SELECT film.title,
# CASE film.rating
# WHEN 'G' THEN 'General Audience'
# WHEN 'PG' THEN 'Parental Guidance'
# WHEN 'PG-13' THEN 'Parents Strongly Cautioned'
# WHEN 'R' THEN 'Restricted'
# ELSE 'Not Rated'
# END AS rating_description
case_when_select(selecto, when_clauses, opts \\ [])
Add a searched CASE expression to the select fields.
Searched CASE expressions evaluate multiple conditions and return results based on the first true condition. This enables complex conditional logic.
parameters
Parameters
selecto- The Selecto instancewhen_clauses- List of {conditions, result} tuplesopts- Options including :else and :as
examples
Examples
# Customer tier based on payment totals
selecto
|> Selecto.case_when_select([
{[{"payment_total", {:>, 100}}], "Premium"},
{[{"payment_total", {:between, 50, 100}}], "Standard"},
{[{"payment_total", {:>, 0}}], "Basic"}
], else: "No Purchases", as: "customer_tier")
|> Selecto.select(["customer.first_name", "customer_tier"])
# Multiple conditions per WHEN clause
selecto
|> Selecto.case_when_select([
{[{"film.rating", "R"}, {"film.length", {:>, 120}}], "Long Adult Film"},
{[{"film.rating", "G"}, {"film.special_features", {:like, "%Family%"}}], "Family Film"}
], else: "Regular Film", as: "film_category")
# Generated SQL:
# SELECT customer.first_name,
# CASE
# WHEN payment_total > $1 THEN $2
# WHEN payment_total BETWEEN $3 AND $4 THEN $5
# WHEN payment_total > $6 THEN $7
# ELSE $8
# END AS customer_tier
columns(selecto)
configure(domain, postgrex_opts, opts \\ [])
@spec configure(Selecto.Types.domain(), Postgrex.conn(), keyword()) :: t()
Generate a selecto structure from a domain configuration and database connection.
## Parameters
domain- Domain configuration map (see domain configuration docs)postgrex_opts- Postgrex connection options, PID, or pooled connectionopts- Configuration options
## Options
:validate- (boolean, default: true) Whether to validate the domain configuration before processing. Whentrue, will raiseSelecto.DomainValidator.ValidationErrorif the domain has structural issues like missing schemas, circular join dependencies, or invalid advanced join configurations.:pool- (boolean, default: false) Whether to enable connection pooling:pool_options- Connection pool configuration options:adapter- (module, default: Selecto.DB.PostgreSQL) Database adapter module
## Validation
Domain validation checks for:
- Required top-level keys (source, schemas)
- Schema structural integrity (required keys, column definitions)
- Association references to valid schemas
- Join references to existing associations
- Join dependency cycles that would cause infinite recursion
- Advanced join type requirements (dimension keys, hierarchy parameters, etc.)
- Field reference validity in filters and selectors
## Examples
# Basic usage (validation enabled by default)
selecto = Selecto.configure(domain, postgrex_opts)
# With connection pooling
selecto = Selecto.configure(domain, postgrex_opts, pool: true)
# Custom pool configuration
pool_opts = [pool_size: 20, max_overflow: 10]
selecto = Selecto.configure(domain, postgrex_opts, pool: true, pool_options: pool_opts)
# Using existing pooled connection
{:ok, pool} = Selecto.ConnectionPool.start_pool(postgrex_opts)
selecto = Selecto.configure(domain, {:pool, pool})
# Disable validation for performance-critical scenarios
selecto = Selecto.configure(domain, postgrex_opts, validate: false)
# With Ecto repository and schema
selecto = Selecto.from_ecto(MyApp.Repo, MyApp.User)
# Validation can also be called explicitly
:ok = Selecto.DomainValidator.validate_domain!(domain)
selecto = Selecto.configure(domain, postgrex_opts)
domain(selecto)
@spec domain(t()) :: Selecto.Types.domain()
domain_data(selecto)
ensure_tenant_scope!(selecto, opts \\ [])
Raise if tenant scope is required and missing.
except(left_query, right_query, opts \\ [])
Create an EXCEPT set operation between two queries.
Returns rows from the first query that don't appear in the second query.
options
Options
:all- Use EXCEPT ALL to include duplicates in difference (default: false):column_mapping- Map columns between incompatible schemas
examples
Examples
# Find free users (all users except premium)
all_users |> Selecto.except(premium_users)
# Include duplicates in difference
query1 |> Selecto.except(query2, all: true)
execute(selecto, opts \\ [])
@spec execute(Selecto.Types.t(), Selecto.Types.execute_options()) :: Selecto.Types.safe_execute_result()
Generate and run the query, returning {:ok, result} or {:error, reason}.
Non-raising version that returns tagged tuples for better error handling. Result format: {:ok, {rows, columns, aliases}} | {:error, reason}
## Examples
case Selecto.execute(selecto) do
{:ok, {rows, columns, aliases}} ->
# Handle successful query
process_results(rows, columns)
{:error, reason} ->
# Handle database error
Logger.error("Query failed: #{inspect(reason)}")
end
execute_one(selecto, opts \\ [])
@spec execute_one(Selecto.Types.t(), Selecto.Types.execute_options()) :: Selecto.Types.safe_execute_one_result()
Execute a query expecting exactly one row, returning {:ok, row} or {:error, reason}.
Useful for queries that should return a single record (e.g., with LIMIT 1 or aggregate functions). Returns an error if zero rows or multiple rows are returned.
## Examples
case Selecto.execute_one(selecto) do
{:ok, row} ->
# Handle single row result
process_single_result(row)
{:error, :no_results} ->
# Handle case where no rows were found
{:error, :multiple_results} ->
# Handle case where multiple rows were found
{:error, error} ->
# Handle database or other errors
end
execute_shape(selecto, opts \\ [])
@spec execute_shape(t(), Selecto.Types.execute_options()) :: {:ok, list()} | {:error, Selecto.Error.t()}
Execute a query configured with select_shape/2 and return shaped rows.
Returns {:ok, shaped_rows} where each row mirrors the selection shape.
execute_stream(selecto, opts \\ [])
@spec execute_stream( Selecto.Types.t(), keyword() ) :: Selecto.Types.safe_execute_stream_result()
Execute a query as a database-backed stream.
Returns a stream of {row, columns, aliases} tuples for incremental result
consumption.
options
Options
:max_rows- PostgreSQL cursor batch size (default500):receive_timeout- stream consumer wait timeout in ms (default60000):queue_timeout- internal task yield timeout in ms (default100):stream_timeout- transaction timeout for cursor execution (default30000)
notes
Notes
- Direct PostgreSQL connections use cursor-backed streaming.
- Adapter-backed streaming requires
adapter.stream/4support. - Ecto repo and pooled PostgreSQL stream paths currently return structured
:validation_errorresponses.
execute_with_metadata(selecto, opts \\ [])
@spec execute_with_metadata(Selecto.Types.t(), Selecto.Types.execute_options()) :: {:ok, Selecto.Types.execute_result(), map()} | {:error, Selecto.Error.t()}
Execute a query and return results with metadata including SQL, params, and execution time.
parameters
Parameters
selecto- The Selecto struct containing connection and query infoopts- Execution options
returns
Returns
{:ok, result, metadata}- Successful execution with results and metadata{:error, error}- Execution failure with detailed error
The metadata map includes:
:sql- The generated SQL query string:params- The query parameters:execution_time- Query execution time in milliseconds
examples
Examples
case Selecto.execute_with_metadata(selecto) do
{:ok, {rows, columns, aliases}, _metadata} ->
# Process successful results with metadata
handle_results(rows, columns, aliases)
{:error, error} ->
# Handle database error
Logger.error("Query failed: #{inspect(error)}")
end
explain(selecto, opts \\ [])
@spec explain( t(), keyword() ) :: {:ok, map()} | {:error, Selecto.Error.t()}
Run EXPLAIN for a query and return plan details.
explain_analyze(selecto, opts \\ [])
@spec explain_analyze( t(), keyword() ) :: {:ok, map()} | {:error, Selecto.Error.t()}
Run EXPLAIN ANALYZE for a query and return plan details.
extensions(selecto)
field(selecto, field_name)
@spec field(t(), Selecto.Types.field_name()) :: map() | nil
field_suggestions(selecto, partial_name)
Get field suggestions for autocomplete or error recovery.
filter(selecto, filters_or_filter)
@spec filter(t(), [Selecto.Types.filter()]) :: t()
@spec filter(t(), Selecto.Types.filter()) :: t()
Add a filter to selecto. Send in a tuple with field name and filter value.
filters(selecto)
format_sql(sql, opts \\ [])
Format SQL output for readability.
from_ecto(repo, schema, opts \\ [])
Configure Selecto from an Ecto repository and schema.
This convenience function automatically introspects the Ecto schema and configures Selecto with the appropriate domain and database connection.
## Parameters
repo- The Ecto repository module (e.g., MyApp.Repo)schema- The Ecto schema module to use as the source tableopts- Configuration options (passed to EctoAdapter.configure/3)
## Examples
# Basic usage
selecto = Selecto.from_ecto(MyApp.Repo, MyApp.User)
# With joins and options
selecto = Selecto.from_ecto(MyApp.Repo, MyApp.User,
joins: [:posts, :profile],
redact_fields: [:password_hash]
)
# With validation
selecto = Selecto.from_ecto(MyApp.Repo, MyApp.User, validate: true)
gen_sql(selecto, opts)
group_by(selecto, groups)
@spec group_by(t(), [Selecto.Types.field_name()]) :: t()
@spec group_by(t(), Selecto.Types.field_name()) :: t()
Add to the Group By clause.
highlight_sql(sql, style)
Apply optional highlighting to SQL (:ansi or :markdown).
infer_type(selecto, expression)
@spec infer_type(t(), term()) :: {:ok, Selecto.TypeSystem.sql_type()} | {:error, term()}
Infer the SQL type of an expression.
Returns the type of a field, function, literal, or complex expression. Useful for type checking, validation, and UI components that need type information.
examples
Examples
# Field type lookup
{:ok, :string} = Selecto.infer_type(selecto, "product_name")
# Aggregate function
{:ok, :bigint} = Selecto.infer_type(selecto, {:count, "*"})
# Numeric aggregate
{:ok, :decimal} = Selecto.infer_type(selecto, {:sum, "price"})
# Literal
{:ok, :integer} = Selecto.infer_type(selecto, {:literal, 42})
intersect(left_query, right_query, opts \\ [])
Create an INTERSECT set operation between two queries.
Returns only rows that appear in both queries.
options
Options
:all- Use INTERSECT ALL to include duplicate intersections (default: false):column_mapping- Map columns between incompatible schemas
examples
Examples
# Find users who are both active and premium
active_users |> Selecto.intersect(premium_users)
# Include duplicate intersections
query1 |> Selecto.intersect(query2, all: true)
join(selecto, join_id, options \\ [])
Enable a join from the domain configuration or add a custom join dynamically.
This allows adding joins at runtime that either:
- Enable predefined joins from the domain configuration
- Add completely custom joins not in the domain
parameters
Parameters
join_id- The join identifier (atom)options- Optional configuration overrides
options
Options
:type- Join type (:left, :inner, :right, :full). Default: :left:source- Source table name (required for custom joins):on- Join conditions as list of maps with :left and :right keys:owner_key- The key on the parent table:related_key- The key on the joined table:fields- Map of field configurations to expose from the joined table
examples
Examples
# Enable domain-configured join
selecto |> Selecto.join(:category)
# Custom join with explicit configuration
selecto |> Selecto.join(:audit_log,
source: "audit_logs",
on: [%{left: "id", right: "record_id"}],
type: :left,
fields: %{
action: %{type: :string},
created_at: %{type: :naive_datetime}
}
)
join_parameterize(selecto, join_id, parameter, options \\ [])
Create a parameterized instance of an existing join.
Parameterized joins allow the same association to be joined multiple times
with different filter conditions. The parameter creates a unique instance
that can be referenced using dot notation: join_name:parameter.field_name
parameters
Parameters
join_id- Base join identifier to parameterizeparameter- Unique parameter value to identify this instanceoptions- Filter conditions and options
examples
Examples
# Create parameterized join for electronics products
selecto
|> Selecto.join_parameterize(:products, "electronics", category_id: 1)
|> Selecto.select(["products:electronics.product_name"])
# Multiple parameterized instances for comparison
selecto
|> Selecto.join_parameterize(:orders, "active", status: "active")
|> Selecto.join_parameterize(:orders, "completed", status: "completed")
|> Selecto.select([
"orders:active.total as active_total",
"orders:completed.total as completed_total"
])
join_subquery(selecto, join_id, join_selecto, options \\ [])
Join with another Selecto query as a subquery.
This creates a join using a separate Selecto query as the right side, enabling complex subquery joins for aggregations and derived tables.
parameters
Parameters
join_id- Identifier for this joinjoin_selecto- The Selecto struct to use as subqueryoptions- Join configuration
options
Options
:type- Join type (:left, :inner, :right, :full). Default: :left:on- Join conditions referencing the subquery alias
examples
Examples
# Create a subquery for aggregated data
order_totals = Selecto.configure(order_domain, connection)
|> Selecto.select(["customer_id", {:sum, "total", as: "total_spent"}])
|> Selecto.group_by(["customer_id"])
# Join aggregated subquery to main query
selecto
|> Selecto.join_subquery(:customer_totals, order_totals,
on: [%{left: "customer_id", right: "customer_id"}]
)
|> Selecto.select(["name", "customer_totals.total_spent"])
joins(selecto)
json_filter(selecto, json_filters, opts \\ [])
Add JSON operations to WHERE clauses for filtering with PostgreSQL JSON/JSONB functionality.
Supports JSON containment, existence, and comparison operations.
parameters
Parameters
selecto- The Selecto instancejson_filters- List of JSON filter tuples or single filteropts- Options (reserved for future use)
examples
Examples
# JSON containment and existence
selecto
|> Selecto.json_filter([
{:json_contains, "metadata", %{"category" => "electronics"}},
{:json_path_exists, "metadata", "$.specs.warranty"}
])
# JSON path comparison
selecto
|> Selecto.json_filter([
{:json_extract_text, "settings", "$.theme", {:=, "dark"}},
{:json_extract, "data", "$.priority", {:>, 5}}
])
# Single JSON filter
selecto
|> Selecto.json_filter({:json_exists, "tags", "electronics"})
json_order_by(selecto, json_sorts, opts \\ [])
Add JSON operations to ORDER BY clauses for sorting with PostgreSQL JSON/JSONB functionality.
parameters
Parameters
selecto- The Selecto instancejson_sorts- List of JSON sort tuples or single sortopts- Options (reserved for future use)
examples
Examples
# Sort by JSON path values
selecto
|> Selecto.json_order_by([
{:json_extract, "metadata", "$.priority", :desc},
{:json_extract_text, "data", "$.created_at", :asc}
])
# Single JSON sort
selecto
|> Selecto.json_order_by({:json_extract, "settings", "$.sort_order"})
json_select(selecto, json_operations, opts \\ [])
Add JSON operations to SELECT clauses for PostgreSQL JSON/JSONB functionality.
Supports JSON path extraction, aggregation, construction, and manipulation operations.
parameters
Parameters
selecto- The Selecto instancejson_operations- List of JSON operation tuples or single operationopts- Options (reserved for future use)
examples
Examples
# JSON path extraction
selecto
|> Selecto.json_select([
{:json_extract, "metadata", "$.category", as: "category"},
{:json_extract, "metadata", "$.specs.weight", as: "weight"}
])
# JSON aggregation
selecto
|> Selecto.json_select([
{:json_agg, "product_name", as: "products"},
{:json_object_agg, "product_id", "price", as: "price_map"}
])
|> Selecto.group_by(["category"])
# Single JSON operation
selecto
|> Selecto.json_select({:json_extract, "data", "$.status", as: "status"})
lateral_join(selecto, arg2, arg3 \\ [], arg4 \\ nil, arg5 \\ [])
Add a LATERAL join to the query.
LATERAL joins allow the right side of the join to reference columns from the left side, enabling powerful correlated subquery patterns.
parameters
Parameters
join_type- Type of join (:left, :inner, :right, :full)subquery_builder_or_function- Function that builds correlated subquery or table function tuplealias_name- Alias for the LATERAL join resultsopts- Additional options
examples
Examples
# LATERAL join with correlated subquery
selecto
|> Selecto.lateral_join(
:left,
fn base_query ->
Selecto.configure(rental_domain, connection)
|> Selecto.select([{:func, "COUNT", ["*"], as: "rental_count"}])
|> Selecto.filter([{"customer_id", {:ref, "customer.customer_id"}}])
|> Selecto.limit(5)
end,
"recent_rentals"
)
# LATERAL join with table function
selecto
|> Selecto.lateral_join(
:inner,
{:unnest, "film.special_features"},
"features"
)
# LATERAL join with generate_series
selecto
|> Selecto.lateral_join(
:inner,
{:function, :generate_series, [1, 10]},
"numbers"
)
limit(selecto, limit_value)
@spec limit(t(), non_neg_integer()) :: t()
Limit the number of rows returned by the query.
examples
Examples
# Limit to 10 rows
selecto |> Selecto.limit(10)
# Limit with offset for pagination
selecto |> Selecto.limit(10) |> Selecto.offset(20)
offset(selecto, offset_value)
@spec offset(t(), non_neg_integer()) :: t()
Set the offset for the query results.
examples
Examples
# Skip first 20 rows
selecto |> Selecto.offset(20)
# Pagination: page 3 with 10 items per page
selecto |> Selecto.limit(10) |> Selecto.offset(20)
order_by(selecto, orders)
@spec order_by(t(), [Selecto.Types.order_spec()]) :: t()
@spec order_by(t(), Selecto.Types.order_spec()) :: t()
Add to the Order By clause.
pivot(selecto, target_schema, opts \\ [])
Pivot the query to focus on a different table while preserving existing context.
This allows you to retarget a Selecto query from the source table to any joined table, while preserving existing filters through subqueries.
examples
Examples
# Pivot from events to orders while preserving event filters
selecto
|> Selecto.filter([{"event_id", 123}])
|> Selecto.pivot(:orders)
|> Selecto.select(["product_name", "quantity"])
options
Options
:preserve_filters- Whether to preserve existing filters (default: true):subquery_strategy- How to generate the subquery (:in,:exists,:join)
See Selecto.Pivot module for more details.
post_pivot_filter(selecto, filters_or_filter)
@spec post_pivot_filter(t(), [Selecto.Types.filter()]) :: t()
@spec post_pivot_filter(t(), Selecto.Types.filter()) :: t()
Append filters explicitly to the post-pivot filter list.
These filters apply to the pivoted target root.
post_pivot_filters(selecto)
@spec post_pivot_filters(t()) :: [Selecto.Types.filter()]
Read post-pivot filters from the query set (set.post_pivot_filters).
pre_pivot_filter(selecto, filters_or_filter)
@spec pre_pivot_filter(t(), [Selecto.Types.filter()]) :: t()
@spec pre_pivot_filter(t(), Selecto.Types.filter()) :: t()
Append filters explicitly to the pre-pivot filter list.
These filters stay attached to the original root side when using pivot/3.
pre_pivot_filters(selecto)
@spec pre_pivot_filters(t()) :: [Selecto.Types.filter()]
Read pre-pivot filters from the query set (set.filtered).
query_filters(selecto, opts \\ [])
@spec query_filters( t(), keyword() ) :: [Selecto.Types.filter()]
Return query filters from legacy and current filter buckets.
Options:
:include_post_pivot(default:true)
require_tenant_filter(selecto, filter)
@spec require_tenant_filter(t(), Selecto.Types.filter()) :: t()
Add a required tenant filter to query state.
require_tenant_filter(selecto, tenant_field, tenant_id)
required_filters(selecto)
@spec required_filters(t()) :: [Selecto.Types.filter()]
Return required filters currently attached to the query.
This includes domain-level required filters and tenant-scope required filters attached at runtime.
resolve_field(selecto, field)
@spec resolve_field(t(), Selecto.Types.field_name()) :: {:ok, map()} | {:error, term()}
Enhanced field resolution with disambiguation and error handling.
Provides detailed field information and helpful error messages.
select(selecto, fields_or_field)
@spec select(t(), [Selecto.Types.selector()]) :: t()
@spec select(t(), Selecto.Types.selector()) :: t()
Add a field to the Select list. Send in one or a list of field names or selectable tuples.
select_shape(selecto, shape)
Compile a nested selection shape and attach it to the query.
This is an opt-in structured selection API. Use execute_shape/2 to
materialize results into the same list/tuple structure.
Nested lists/tuples that only reference a single joined schema are treated as subselect nodes.
set(selecto)
@spec set(t()) :: Selecto.Types.query_set()
See Selecto.Fields.set/1.
source_table(selecto)
@spec source_table(t()) :: Selecto.Types.table_name() | nil
subselect(selecto, field_specs, opts \\ [])
Add subselect fields to return related data as aggregated arrays.
This prevents result set denormalization while maintaining relational context by returning related data as JSON arrays, PostgreSQL arrays, or other formats.
examples
Examples
# Basic subselect - get orders as JSON for each attendee
selecto
|> Selecto.select(["attendee[name]"])
|> Selecto.subselect(["order[product_name]", "order[quantity]"])
# With custom configuration
selecto
|> Selecto.subselect([
%{
fields: ["product_name", "quantity"],
target_schema: :order,
format: :json_agg,
alias: "order_items"
}
])
options
Options
:format- Aggregation format (:json_agg,:array_agg,:string_agg,:count):alias_prefix- Prefix for generated field aliases
See Selecto.Subselect module for more details.
tenant(selecto)
Read tenant context from query state.
tenant_required?(selecto, opts \\ [])
Return whether tenant scope is required for this query.
to_sql(selecto, opts \\ [])
Generate SQL without executing - useful for debugging and caching.
Supports optional readability controls:
pretty: truehighlight: :ansi | :markdown
type_category(type)
@spec type_category(Selecto.TypeSystem.sql_type()) :: Selecto.TypeSystem.type_category()
Get the type category for a given SQL type.
Categories: :numeric, :string, :boolean, :datetime, :json, :array, :binary, :uuid, :unknown
types_compatible?(type1, type2)
@spec types_compatible?(Selecto.TypeSystem.sql_type(), Selecto.TypeSystem.sql_type()) :: boolean()
Check if two SQL types are compatible for comparisons or assignments.
examples
Examples
true = Selecto.types_compatible?(:integer, :decimal)
false = Selecto.types_compatible?(:string, :boolean)
union(left_query, right_query, opts \\ [])
Create a UNION set operation between two queries.
Combines results from multiple queries using UNION or UNION ALL. All queries must have compatible column counts and types.
options
Options
:all- Use UNION ALL to include duplicates (default: false):column_mapping- Map columns between incompatible schemas
examples
Examples
# Basic UNION (removes duplicates)
query1 |> Selecto.union(query2)
# UNION ALL (includes duplicates, faster)
query1 |> Selecto.union(query2, all: true)
# UNION with column mapping
customers |> Selecto.union(vendors,
column_mapping: [
{"name", "company_name"},
{"email", "contact_email"}
]
)
unnest(selecto, array_field, opts \\ [])
Add an UNNEST operation to expand array columns into rows.
UNNEST transforms array values into a set of rows, one for each array element. Can optionally include ordinality to track position in the array.
examples
Examples
# Basic unnest
selecto |> Selecto.unnest("tags", as: "tag")
# Unnest with ordinality (includes position)
selecto |> Selecto.unnest("tags", as: "tag", ordinality: "tag_position")
# Multiple unnests (will be cross-joined)
selecto
|> Selecto.unnest("tags", as: "tag")
|> Selecto.unnest("categories", as: "category")
validate_tenant_scope(selecto, opts \\ [])
@spec validate_tenant_scope( t(), keyword() ) :: :ok | {:error, Selecto.Error.t()}
Validate tenant scope and return :ok or structured validation error.
window_function(selecto, function, arguments \\ [], options)
Add a window function to the query.
Window functions provide analytical capabilities over a set of rows related to the current row, without grouping rows into a single result.
examples
Examples
# Add row numbers within each category
selecto |> Selecto.window_function(:row_number,
over: [partition_by: ["category"], order_by: ["created_at"]])
# Calculate running total
selecto |> Selecto.window_function(:sum, ["amount"],
over: [partition_by: ["user_id"], order_by: ["date"]],
as: "running_total")
# Get previous value for comparison
selecto |> Selecto.window_function(:lag, ["amount", 1],
over: [partition_by: ["user_id"], order_by: ["date"]],
as: "prev_amount")
with_cte(selecto, name, query_builder, opts \\ [])
Add a Common Table Expression (CTE) to the query using WITH clause.
CTEs provide a way to create temporary named result sets that can be referenced within the main query, enabling query modularity and readability.
parameters
Parameters
selecto- The Selecto instancename- CTE name (must be valid SQL identifier)query_builder- Function that returns a Selecto query for the CTEopts- Options including :columns, :dependencies
examples
Examples
# Simple CTE for filtering
selecto
|> Selecto.with_cte("active_customers", fn ->
Selecto.configure(customer_domain, connection)
|> Selecto.filter([{"active", true}])
end)
|> Selecto.select(["film.title", "active_customers.first_name"])
|> Selecto.join(:inner, "active_customers",
on: "rental.customer_id = active_customers.customer_id")
# CTE with explicit columns
selecto
|> Selecto.with_cte("customer_stats",
fn ->
Selecto.configure(customer_domain, connection)
|> Selecto.select(["customer_id", {:func, "COUNT", ["rental_id"], as: "rental_count"}])
|> Selecto.join(:left, "rental", on: "customer.customer_id = rental.customer_id")
|> Selecto.group_by(["customer_id"])
end,
columns: ["customer_id", "rental_count"]
)
# Generated SQL:
# WITH active_customers AS (
# SELECT * FROM customer WHERE active = true
# )
# SELECT film.title, active_customers.first_name
# FROM film
# INNER JOIN active_customers ON rental.customer_id = active_customers.customer_id
with_ctes(selecto, cte_specs)
Add multiple CTEs to the query in a single operation.
Useful for complex queries that require multiple temporary result sets. CTEs will be automatically ordered based on their dependencies.
parameters
Parameters
selecto- The Selecto instancecte_specs- List of CTE specifications created with create_cte/3
examples
Examples
# Multiple related CTEs
active_customers_cte = Selecto.Advanced.CTE.create_cte("active_customers", fn ->
Selecto.configure(customer_domain, connection)
|> Selecto.filter([{"active", true}])
end)
high_value_cte = Selecto.Advanced.CTE.create_cte("high_value_customers", fn ->
Selecto.configure(customer_domain, connection)
|> Selecto.aggregate([{"payment.amount", :sum, as: "total_spent"}])
|> Selecto.join(:inner, "payment", on: "customer.customer_id = payment.customer_id")
|> Selecto.group_by(["customer.customer_id"])
|> Selecto.having([{"total_spent", {:>, 100}}])
end, dependencies: ["active_customers"])
selecto
|> Selecto.with_ctes([active_customers_cte, high_value_cte])
|> Selecto.select(["film.title", "high_value_customers.total_spent"])
with_recursive_cte(selecto, arg2, arg3, arg4 \\ nil, arg5 \\ [])
Add a recursive Common Table Expression (CTE) to the query.
Recursive CTEs enable hierarchical queries by combining an anchor query with a recursive query that references the CTE itself.
parameters
Parameters
selecto- The Selecto instancename- CTE name (must be valid SQL identifier)opts- Options with :base_query and :recursive_query functions
examples
Examples
# Hierarchical employee structure
selecto
|> Selecto.with_recursive_cte("employee_hierarchy",
base_query: fn ->
# Anchor: top-level managers
Selecto.configure(employee_domain, connection)
|> Selecto.select(["employee_id", "name", "manager_id", {:literal, 0, as: "level"}])
|> Selecto.filter([{"manager_id", nil}])
end,
recursive_query: fn cte_ref ->
# Recursive: subordinates
Selecto.configure(employee_domain, connection)
|> Selecto.select(["employee.employee_id", "employee.name", "employee.manager_id",
{:func, "employee_hierarchy.level + 1", as: "level"}])
|> Selecto.join(:inner, cte_ref, on: "employee.manager_id = employee_hierarchy.employee_id")
end
)
|> Selecto.join(:inner, "employee_hierarchy",
on: "selecto_root.employee_id = employee_hierarchy.employee_id")
|> Selecto.select([
"employee_hierarchy.employee_id",
"employee_hierarchy.name",
"employee_hierarchy.level"
])
|> Selecto.order_by([{"employee_hierarchy.level", :asc}, {"employee_hierarchy.name", :asc}])
# Generated SQL:
# WITH RECURSIVE employee_hierarchy AS (
# SELECT employee_id, name, manager_id, 0 as level
# FROM employee
# WHERE manager_id IS NULL
# UNION ALL
# SELECT employee.employee_id, employee.name, employee.manager_id, employee_hierarchy.level + 1
# FROM employee
# INNER JOIN employee_hierarchy ON employee.manager_id = employee_hierarchy.employee_id
# )
# SELECT employee_hierarchy.employee_id, employee_hierarchy.name, employee_hierarchy.level
# FROM employee
# INNER JOIN employee_hierarchy ON employee.employee_id = employee_hierarchy.employee_id
# ORDER BY employee_hierarchy.level ASC, employee_hierarchy.name ASC
with_tenant(selecto, tenant_context)
Attach tenant context to the query state.
with_values(selecto, data, opts \\ [])
Add a VALUES clause to create an inline table from literal data.
VALUES clauses allow creating inline tables from literal values, useful for data transformations, lookup tables, and testing scenarios.
parameters
Parameters
selecto- The Selecto structdata- List of data rows (lists or maps)opts- Options including:columns(explicit column names) and:as(table alias)
examples
Examples
# Basic VALUES table with explicit columns
selecto
|> Selecto.with_values([
["PG", "Family Friendly", 1],
["PG-13", "Teen", 2],
["R", "Adult", 3]
],
columns: ["rating_code", "description", "sort_order"],
as: "rating_lookup"
)
# Map-based VALUES (columns inferred from keys)
selecto
|> Selecto.with_values([
%{month: 1, name: "January", days: 31},
%{month: 2, name: "February", days: 28},
%{month: 3, name: "March", days: 31}
], as: "months")
# Generated SQL:
# WITH rating_lookup (rating_code, description, sort_order) AS (
# VALUES ('PG', 'Family Friendly', 1),
# ('PG-13', 'Teen', 2),
# ('R', 'Adult', 3)
# )