| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The delete_all recipe isn't obsolete — it's a different tool (DB-agnostic, validation-friendly, full-row replace). Present both approaches with their trade-offs and lead with the native :on_duplicate_key_update upsert, trimming the adapter notes to the PG/SQLite vs MySQL option shapes.
| Back | FazBrowse Home | New Git URL |
Follow-up to #220.
The "Update existing records by id" README section led with the delete_all recipe as the primary way, which reads as if it is outdated next to the native :on_duplicate_key_update upsert added in #220. It is not — it is a different tool. This restructures the section so the reader can pick the right one:
Docs only — no code changes.