Skip to content

Handle empty parameters in prepared statement execution#230

Closed
zag2me wants to merge 1 commit into
ezSQL:masterfrom
zag2me:patch-1
Closed

Handle empty parameters in prepared statement execution#230
zag2me wants to merge 1 commit into
ezSQL:masterfrom
zag2me:patch-1

Conversation

@zag2me

@zag2me zag2me commented May 14, 2026

Copy link
Copy Markdown
Contributor

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

@TheTechsTech TheTechsTech left a comment

Copy link
Copy Markdown
Contributor

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?

@zag2me

zag2me commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

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?

Yes you are right, sorry this was an AI fix from a production environment. My bad. Will close.

@zag2me zag2me closed this Jun 12, 2026
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