Bring a row to local

Local Snapshot starts from a stable PostgreSQL table row, not an arbitrary query result.

Start from Table Mode

1. Open a PostgreSQL base table.
2. Select the row that reproduces the issue.
3. Right-click the row and choose Bring to Local….

The same action is available from Row Detail when the current table is eligible.

QueryDeck shows the action only when the table has a declared primary key. Composite primary keys are supported.

What happens next

QueryDeck automatically inspects the source and builds a relationship plan.

The plan starts from the selected primary key and follows:

• required referenced parent rows;
• referencing child rows within the snapshot guardrails;
• composite foreign keys as one logical relationship.

You see the number of rows and tables before anything is copied.

For example, one account row might expand to:

accounts       1 row
orders         2 rows
order_items    3 rows
sessions       1 row
--------------------
total          7 rows

Review the scope

The default view keeps the relationship plan compact. Expand the details when you want to inspect which tables are included.

QueryDeck does not persist the source row payloads as part of the plan. The row set is recomputed at Run time inside a coherent read-only source transaction.

If the source data changed after your review, QueryDeck can invalidate the reviewed plan instead of silently copying a different case.

Production sources

Using a connection marked Production adds a device-owner authentication gate for the Local Snapshot workflow.

A dedicated read-only database role is still recommended for production sources.

Next

• Review privacy and sanitization
• Choose the local destination