One-command materialization

What it is

materialize_layer() runs the whole pipeline at once: it introspects the AGOL layer, generates the DDL (tables, constraints, lookups, triggers), applies it to a schema you choose (default data), and backfills the existing rows from AGOL. It's idempotent — safe to re-run.

Why it matters

• One call, full result. Introspect → DDL → apply → backfill, no manual glue steps.
• Idempotent. Re-run to converge; no duplicate tables or broken constraints.
• Re-runnable. Pair with sync_schema() to catch and apply schema drift later.
• Your schema, your tables. Materialized tables are ordinary Postgres in the schema you pick — not locked away.

See it

SELECT agol_fdw.materialize_layer(
  layer_url := 'https://services.arcgis.com/.../FeatureServer/0',
  layer_name := 'poles',
  target_schema := 'data'
);

-- result: data.poles exists as a real PostGIS table,
-- with geometry, domains, subtypes, rules, relationships,
-- and contingent values — and it's already populated.

Related

← Back to home