Skip to content

Commit

Permalink
Document the customized column display functionality
Browse files Browse the repository at this point in the history
  • Loading branch information
emarsden committed Aug 24, 2024
1 parent 64d83dc commit 11a7109
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 23 deletions.
1 change: 1 addition & 0 deletions doc/src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,5 @@
- [Editing data](./editing.md)
- [Running SQL queries](./sql-query.md)
- [SchemaSpy support](./schemaspy.md)
- [Customizing column display](./custom-display.md)
- [Feedback](./feedback.md)
23 changes: 0 additions & 23 deletions doc/src/editing.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,26 +78,3 @@ To downcase the characters in the current cell, and also update the database:
C-u ! tr '[:upper:]' '[:lower:']
```



## Follow foreign key references

A column that references data in a foreign table (`FOREIGN KEY`) will be shown in blue. If you type
`RET` when point is located on a foreign key reference, PGmacs will jump to the referenced row and column in
the other table. A new row-list buffer is opened; type `q` to come back to the orginal row-list
buffer.

![Following foreign key](img/follow-foreign-key.gif)



## Viewing output from an SQL query

You can also view (but obviously not edit!) the output from an SQL query you enter. Type `e` in a
PGmacs buffer, which will prompt you for an SQL query in the minibuffer, then display the output in
a dedicated temporary buffer. Type `q` to kill the temporary buffer.

Likewise, PGmacs can display the output from an SQL query in an Emacs buffer. Type `E` and it will
prompt you for the buffer name, then display the query output in a dedicated temporary buffer.

![Screenshot table](img/screenshot-sql-query.png)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 11a7109

Please sign in to comment.