docs: fix parameter syntax inconsistency for MySQL and SQLite #4036
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes parameter syntax inconsistency in the howto documentation where examples only showed PostgreSQL syntax (
$1
,$2
), causing confusion and errors for MySQL and SQLite users.Problem
As reported in #3697, the generic howto documentation files showed only PostgreSQL parameter syntax:
$1
,$2
placeholders which only work with PostgreSQLSolution
Updated four key documentation files to include database-specific examples:
Modified Files:
docs/howto/update.md
docs/howto/insert.md
docs/howto/delete.md
docs/howto/select.md
Changes Made:
✅ Added database-specific sections with clear syntax examples:
$1
,$2
syntax?
placeholder syntax✅ Added explanatory notes about parameter binding differences
✅ Maintained existing Go code examples (they remain database-agnostic)
✅ Added clarification about MySQL not supporting
RETURNING
clauseExample of Changes
Before:
After:
Impact
Test Plan
Fixes #3697
🤖 Generated with Claude Code