Correction Policy
DuckDB Lab is committed to maintaining technical accuracy. If you find errors in our articles, we welcome and actively address them through the following mechanism.
Scope of Corrections
The following types of errors will be actively corrected:
- Technical factual errors: Incorrect DuckDB API, configuration parameters, or syntax descriptions
- Code errors: Code examples that don’t run or produce expected results
- Version information errors: Inaccurate DuckDB version numbers or feature availability descriptions
- Benchmark data errors: Incorrect test environment, methodology, or results
- Outdated information: Features that have changed after DuckDB upgrades
How to Report Errors
| Method | Description |
|---|---|
| GitHub Issue | Submit an issue at duckdb-blog with the article link and error description |
Send to [email protected] with subject format: [Correction] Article Title | |
| Pull Request | If you have accurate corrections, you can submit a PR directly |
Correction Process
- Receive Report — We acknowledge error reports within 48 hours
- Verify Issue — Reproduce the problem in a test environment to confirm the error
- Execute Correction — Update the article content, fix code or data
- Record Changes — Add a correction note at the bottom of the article (see format below)
- Notify Reporter — Inform the reporter via Issue or email of the correction result
Correction Record Format
Corrected articles will include the following note at the bottom:
---
## Correction History
| Date | Correction | Reporter |
|------|-----------|----------|
| 2026-09-12 | Fixed incorrect XXX description | @username |
Our Commitment
- All confirmed technical errors will be corrected
- Corrected articles retain correction history for transparency
- We regularly review and update existing articles to ensure timeliness
- We encourage community participation in content quality improvement
Thank you for helping DuckDB Lab maintain high content quality.
Last updated: 2026-09-12