Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Handle empty parameters in prepared statement execution#230

Open
zag2me wants to merge 1 commit into
ezSQL:masterezSQL/ezsql:masterfrom
zag2me:patch-1zag2me/ezsql:patch-1Copy head branch name to clipboard
Open

Handle empty parameters in prepared statement execution#230
zag2me wants to merge 1 commit into
ezSQL:masterezSQL/ezsql:masterfrom
zag2me:patch-1zag2me/ezsql:patch-1Copy head branch name to clipboard

Conversation

@zag2me
Copy link
Copy Markdown
Contributor

@zag2me zag2me commented May 14, 2026

Add check for empty parameters before executing statement. query_prepared() now safely executes queries with no bound params instead of crashing on empty bind_param() types

Add check for empty parameters before executing statement. query_prepared() now safely executes queries with no bound params instead of crashing on empty bind_param() types
Copy link
Copy Markdown
Contributor

@TheTechsTech TheTechsTech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to provide something reproducible that will crash.

The query_prepared call allows for $param to be null.
You not fixing any real issue, seems to be creating one instead.

What are you writing that allows it to be or could be null/empty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.