Skip to content

Remove em dashes from docs, per the project style rule #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdatcmd merged 1 commit into from
Jul 6, 2026
Merged

Remove em dashes from docs, per the project style rule #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ and the project aims to follow [Semantic Versioning](https://semver.org/).
- **Transforms reach nested contexts.** A declared `jsonb`/`hstore` transform
now also applies to values of that type inside composite argument/result
fields, `RETURNS SETOF`/`return_next` rows, and a trigger's `$_TD` rows
(including the `'MODIFY'` return) — not only as top-level arguments and
(including the `'MODIFY'` return), not only as top-level arguments and
results. Rows read back through SPI are still left in text form.
- **Structured `pg_raise`.** `pg_raise(level, message [, detail [, hint [,
sqlstate]]])` now attaches `DETAIL`, `HINT` and (for `ERROR`) a custom
Expand Down
4 changes: 2 additions & 2 deletions doc/plphp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ converts values of that type **inside**:
`'MODIFY'`).

Rows read back through SPI (`spi_exec` / `spi_fetch_row` / cursors) are **not**
transformed — like a value crossing the boundary without a `TRANSFORM` clause,
transformed; like a value crossing the boundary without a `TRANSFORM` clause,
they arrive in their text form.

### Domains
Expand Down Expand Up @@ -519,7 +519,7 @@ the PostgreSQL log.

`pg_raise(level, message [, detail [, hint [, sqlstate]]])` accepts `notice`,
`warning`, or `error`, and optionally attaches a `DETAIL`, a `HINT`, and (for
`error`) a custom five-character `SQLSTATE` — the equivalent of PL/pgSQL's
`error`) a custom five-character `SQLSTATE`, the equivalent of PL/pgSQL's
`RAISE ... USING`:

```php
Expand Down
Loading