docs: fix parameter syntax inconsistency for MySQL and SQLite#4036
Merged
kyleconroy merged 1 commit intosqlc-dev:mainfrom Aug 2, 2025
Merged
docs: fix parameter syntax inconsistency for MySQL and SQLite#4036kyleconroy merged 1 commit intosqlc-dev:mainfrom
kyleconroy merged 1 commit intosqlc-dev:mainfrom
Conversation
Update howto documentation to include database-specific parameter syntax: - PostgreSQL: $1, $2, etc. - MySQL/SQLite: ? placeholders Changes made to: - docs/howto/update.md - docs/howto/insert.md - docs/howto/delete.md - docs/howto/select.md This resolves confusion where the generic examples only showed PostgreSQL syntax, causing silent failures in MySQL code generation and syntax errors in SQLite. Fixes sqlc-dev#3697 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
kyleconroy
approved these changes
Aug 2, 2025
alfonsodev
pushed a commit
to ExponentiaTeam/sqlc
that referenced
this pull request
Oct 13, 2025
…ev#4036) Update howto documentation to include database-specific parameter syntax: - PostgreSQL: $1, $2, etc. - MySQL/SQLite: ? placeholders Changes made to: - docs/howto/update.md - docs/howto/insert.md - docs/howto/delete.md - docs/howto/select.md This resolves confusion where the generic examples only showed PostgreSQL syntax, causing silent failures in MySQL code generation and syntax errors in SQLite. Fixes sqlc-dev#3697 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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,$2placeholders which only work with PostgreSQLSolution
Updated four key documentation files to include database-specific examples:
Modified Files:
docs/howto/update.mddocs/howto/insert.mddocs/howto/delete.mddocs/howto/select.mdChanges Made:
✅ Added database-specific sections with clear syntax examples:
$1,$2syntax?placeholder syntax✅ Added explanatory notes about parameter binding differences
✅ Maintained existing Go code examples (they remain database-agnostic)
✅ Added clarification about MySQL not supporting
RETURNINGclauseExample of Changes
Before:
After:
Impact
Test Plan
Fixes #3697
🤖 Generated with Claude Code