SqlLib Maintenance & Write Path Preservation

Enforce selectable legacy or ODBC write paths in SqlLib via SQLDB_NEW_WRITE.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JasonVene/CC_MainDev --skill sqllib-maintenance-write-path-preservation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SqlLib Maintenance & Write Path Preservation
Source: https://github.com/JasonVene/CC_MainDev/tree/main/_archive/antigravity/.agent/skills/sqllib_maintenance
Command: npx skills add https://github.com/JasonVene/CC_MainDev --skill sqllib-maintenance-write-path-preservation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Critical rules for maintaining the dual-write path (Legacy vs. ODBC) in SqlLib.

Core Features & Use Cases

  • Coexistence of Old Write and New Write implementations during transition, controlled by SQLDB_NEW_WRITE.
  • Protection of the production fallback code path to ensure stability across builds.
  • Guidance on preserving structure while enabling innovation behind a compile-time flag.

Quick Start

Define the build to enable SQLDB_NEW_WRITE and verify both write paths compile and link.

Frequently Asked Questions about SqlLib Maintenance & Write Path Preservation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain dual-write path stability when toggling between legacy and ODBC implementations in SqlLib?▼

Dual-write path stability is maintained by isolating new ODBC logic behind the SQLDB_NEW_WRITE compile-time flag and preserving the #ifdef blocks to protect the production fallback code path during both development and production builds.

What is the SQLDB_NEW_WRITE compile-time flag used for in C++ database libraries?▼

The SQLDB_NEW_WRITE compile-time flag enables selectable switching between the old text-based legacy write path and the new ODBC write implementation, allowing both paths to coexist during transition without breaking build stability.

How do I enable the new ODBC write path while preserving the legacy text-based write fallback?▼

Define the build configuration to enable SQLDB_NEW_WRITE, then verify that both the legacy text-based write and new ODBC write paths compile and link successfully while keeping shared resources guarded behind the preprocessor directive.

Does the dual-write ODBC transition approach work with existing production build configurations?▼

Yes, the dual-write approach works with production builds by protecting the existing legacy fallback code path and isolating new ODBC logic behind the SQLDB_NEW_WRITE define, ensuring compatibility and stability across all compilation configurations.

Why does my SqlLib build break when adding new ODBC write logic without preprocessor guards?▼

Builds break because new ODBC write logic must be isolated behind the SQLDB_NEW_WRITE compile-time flag and shared resources must be guarded, ensuring the unmodified legacy text-based write path remains intact for production fallback compatibility.

What's the best way to isolate new ODBC write logic during a legacy database library migration?▼

The best approach is using compile-time preprocessor directives like #ifdef SQLDB_NEW_WRITE to isolate new ODBC implementation blocks, guarding shared resources, and maintaining the old text-based write path as a protected fallback throughout the transition.