@mlagie/sql-connector 2.0.8 → 2.0.10

package/releases/2.0.6.md

@@ -1,80 +0,0 @@
-# Release v2.0.6 — Architectural Property Isolation, Query Defusal & Test Coverage Expansion
-
-This emergency structural release addresses a critical data-shadowing bug within the `ModelInstance` hydration cycle where active database column values (e.g., fields named `name`, `schema`, or `data`) overrode the core internal engine structures, mangling runtime query generation. It also introduces a comprehensive overhaul of the test suite to secure maximum coverage.
-
-## 🛠️ The Bug Defusal (Why this was critical)
-
-When `ModelInstance` mapped rows dynamically into getters/setters, a column named `name` from the database would mask `this.name` (the structural reference to the SQL Table Name).
-
-As a result, an injection or ingestion update would mistakenly compile syntax failures like:
-
-```sql
-UPDATE my_value SET `deletedAt` = ... -- Mangled: Used row data instead of Table Name
-```
-
-By migrating all runtime configuration tokens to protected underscored properties (`_tableName`, `_data`, `_schema`), the instance context is now completely hermetic against database row schema payloads.
-
-## Massive Test Coverage Expansion
-
-To ensure the stability and robustness of this release, the unit test suites for both `Model` and `ModelInstance` have been significantly hardened:
-
-- **Edge-Case & Fallback Testing**: Added specialized tests to force controlled failures in deep `try/catch` blocks, guaranteeing that the global engine fallback workflows function flawlessly under corrupted data scenarios.
-
-- **SQL Mechanics Validation**: Built targeted unit tests covering schema dictionary mismatches, complex conditional mapping (e.g., table joins filtering mixed array types), and secondary logic paths inside `updateOne()`, `delete()`, and `deleteOne()`.
-
-- `Database Simulation Coverage`: Implemented strict simulation sequences verifying UUID collision rejections (ensuring `generate_uuid()` handles duplicates properly) and missing response payloads (such as undefined `affectedRows`).
-
-- `Zero-Crash Guarantees`: Hardened utility methods like `getFieldType()` against historical JavaScript edge cases (such as parsing `null` values safely).
-
-## What Was Improved
-
-- `Protected Context Isolation`: Migrated core metadata targets in `ModelInstance.js` to `_tableName`, `_data`, and `_schema`. Database columns can no longer shadow engine properties.
-
-- `Tiret/Hyphen Database Safety`: Wrapped table calls explicitly in SQL backticks (\`) inside `updateOne`, `delete`, and `deleteOne` routines. Tables named with hyphens (like my_value) no longer trigger syntax violations.
-
-- **Rehydration Mapping Consistency**: Standardized downstream sub-instantiations (like `customRequest`) to feed data strictly using the isolated `_tableName` descriptor.
-
-## File Blueprint Updates
-
-`ModelInstance.js`
-
-The updated architecture encapsulates the internal core parameters like this:
-
-```js
-class ModelInstance {
-    constructor(name, data, schema = null) {
-        Object.defineProperties(this, {
-            _tableName: { // 🔒 Fully protected from row data collisions
-                value: name,
-                writable: true,
-                configurable: true,
-                enumerable: false
-            },
-            _data: {
-                value: data,
-                writable: true,
-                configurable: true,
-                enumerable: true
-            },
-            _schema: {
-                value: schema,
-                writable: true,
-                configurable: true,
-                enumerable: false
-            }
-        });
-        
-        // Dynamic row mapping safely bound without property leakage...
-    }
-
-    async updateOne(model) {
-        const setClause = generateCondition(formatObject(model), true);
-        let whereClause = /* ... evaluation matrix using this._schema & this.getRecordData() ... */;
-
-        // Encapsulated Table execution with explicit backticks
-        const sql_request = `UPDATE \`${this._tableName}\` SET ${setClause} WHERE ${whereClause}`;
-        
-        // ... execute transaction safely
-    }
-}
-```

package/releases/2.0.7.md

@@ -1,38 +0,0 @@
-# Release v2.0.7 — COUNT Polymorphism, Aggregation Alias Security & Test Coverage Overhaul
-
-This major release upgrades the query engine by introducing full polymorphic support for the `COUNT` aggregation function (supporting standard, multi-column distinct, and conditional `CASE WHEN` operations). It also fixes a key-aliasing limitation during raw aggregations and strengthens query-building validation boundaries through an extensive unit testing overhaul.
-
-## COUNT Polymorphism (Why this evolution matters)
-
-Previously, the query engine only accepted a raw string parameter for `COUNT` instructions. The engine now dynamically evaluates three distinct structures (String, Array, Object) passed directly from your selection attributes:
-
-- **Multi-Column Distinct Counting**: Passing an array automatically compiles a unified multi-column unique combination statement, removing the need for manual raw SQL workarounds.
-
-- **Conditional Counting (`CASE WHEN`)**: Passing a key/value object cleanly compiles a conditional statement. This allows you to isolate state and status indicators (KPIs) in a single database round-trip without twisting your global query filters.
-
-As a result, complex nullity checks or status distributions are generated natively:
-
-```js
--- Automated nullity indicator compilation example:
-COUNT(CASE WHEN `deletedAt` = NULL THEN 1 END)
-```
-
-## Test Coverage Expansion
-
-To guarantee the stability of these new mechanics and prevent structural regressions, the global unit testing footprint has been exhaustively expanded:
-
-- **Multi-Count Validation**: Added dedicated test pipelines ensuring the syntax of `COUNT(DISTINCT column1, column2)` is perfectly isolated from standard counters.
-
-- **Temporal Nullity Filtering**: Implemented test scenarios covering both `{ deletedAt: null }` and `{ deletedAt: "NOT NULL" }` parameters to verify string state evaluations.
-
-- **Unsupported Input Interception**: Added strict `throw new Error` type boundaries to guarantee that injecting non-compliant values (like booleans or numbers) results in a clean, controlled application crash.
-
-- **Zero-Leak Key Assurances**: Added strict payload assertions ensuring no raw unmapped backticked SQL expressions can escape into the final Node.js JSON output object.
-
-## What Was Improved
-
-- **Automatic Aggregation Fallback Alias**: Enhanced the `buildField` logic inside `buildQuery.js`. If an explicit `as` descriptor is omitted during a column sum (sum), the engine automatically fallbacks to using the targeted column name as the extraction property, blocking raw SQL formula leaks into the final row keys.
-
-- **Orchestrated Order Sorting**: Hardened the `options.orderBy` evaluator array loop to cleanly isolate and support both raw column identifier strings and structured sorting configuration objects `{ field, direction }`.
-
-Documentation Cleanup: Fully aligned the core developer usage guide and documentation files within `README.md` to reflect the updated parameter boundaries and capabilities.

package/releases/2.0.8.md

@@ -1,5 +0,0 @@
-# Release v2.0.8 — Changed
-
-- Updated maintainer username references across the project.
-- No functional changes.
-- No API changes.

package/socket.yml

@@ -1,4 +0,0 @@
-version: 2
-project:
-  # Masquer les alertes des outils de dev/test dans le rapport
-  ignoreDevDependencies: true