Skip to content

ext/pgsql: do not print an object address in the "Unable to jump to row" warnings - #24217

Open
lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:fix/pgsql-error-message-text
Open

lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:fix/pgsql-error-message-text

Conversation

@lacatoire

@lacatoire lacatoire commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

The "Unable to jump to row" warning of pg_fetch_result(), pg_fetch_row()/assoc()/array()/object(), pg_field_prtlen() and pg_field_is_null() printed Z_LVAL_P() of a PgSql\Result object as a "result index", which is the object address. The operand is dropped.

Before:

Warning: pg_fetch_row(): Unable to jump to row 99 on PostgreSQL result index 133586556570360 in ...

After:

Warning: pg_fetch_row(): Unable to jump to row 99 in ...

…row warnings

The "Unable to jump to row" warning of pg_fetch_result(), pg_fetch_row(),
pg_field_prtlen() and pg_field_is_null() appended Z_LVAL_P() of a
PgSql\Result object as a "result index", which is the object address.
Drop the operand.
@lacatoire lacatoire changed the title ext/pgsql: fix wrong names and values in three diagnostics ext/pgsql: do not print an object address in the "Unable to jump to row" warnings Nov 12, 2026
@lacatoire
lacatoire force-pushed the fix/pgsql-error-message-text branch from 5e233c6 to 407034f Compare November 12, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant