Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/examples/obsproc.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,3 +298,25 @@
$ pfs-targetdb-cli insert -c dbconf.toml -t user_pointing pointing_list.ecsv \
--commit --upload_id "aabbccddeeffgghh"
```

## Change `active` status of an `input_catalog`

When an `input_catalog` is no longer active, you can change its `active` status to `false` by the following command:

```console
$ pfs-targetdb-cli update-catalog-active INPUT_CATALOG_ID false -c db_config.toml --commit

Check notice on line 307 in docs/examples/obsproc.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

docs/examples/obsproc.md#L307

Dollar signs used before commands without showing output
```

This is useful and necessary, when a PI updates the target list before the observing run.

In order to check the `input_catalog_id` and `active` status, you can use the following queries on the target database:

```sql
-- with proposal ID pattern
SELECT input_catalog_id, input_catalog_name, upload_id, active
FROM input_catalog WHERE input_catalog_name LIKE '%S25A%' ORDER BY input_catalog_id;

-- or with an upload_id
SELECT input_catalog_id, input_catalog_name, upload_id, active
FROM input_catalog WHERE upload_id='d6e94eae259faf4e';
```
Loading