Handle null values in prepStmt where object #34
Conversation
When a field in the `where` object is null, `prepStmt` now generates an `IS NULL` query instead of `= ?`. This ensures that null values are correctly queried in the database.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
flaregun | c521639 | Commit Preview URL Branch Preview URL |
Dec 30 2025, 06:10 PM |
Modified
d1.jsto check for null values in thewhereobject withinprepStmt. If a value is null, the query string is appended withIS NULLand the value is not added to the bind parameters. If the value is not null, the behavior remains unchanged (= ?and value added to binds). This change allows for querying records with null fields using the object syntax inwhereclause.PR created automatically by Jules for task 17882863614937784580 started by @treeder