替代資料未載齊，為何已成正式使用資料？

先核來源與已訂規則

本例正式表有 A/B，替代須正好同組編號，數量須有值且正數。候選只有 A 並未齊。更正同一交易載 shadow、改正式登記，提交前查真正缺項、多項及寫入錯誤。

已填假設輸入
紀錄	輸入 JSON
原例輸入	{"candidate":[{"id":"A","quantity":2}]}

下載可編輯 CSV ↓

比較兩條實際路徑

未齊候選回復，原 A/B 繼續可見。候選寫入違 CHECK，也留下原資料供使用。核對只涵蓋此有限已訂約定。

錯誤與更正路徑的輸出
路徑	輸出 JSON
錯誤路徑	{"error":null,"current":"shadow","active":[{"id":"A","quantity":2}],"shadow":[{"id":"A","quantity":2}]}
更正路徑	{"error":"incomplete-candidate","current":"original","active":[{"id":"A","quantity":1},{"id":"B","quantity":1}],"shadow":[]}

下載可編輯 CSV ↓

本地 Node.js 程序：22.23.3 或 24.14.1

import {DatabaseSync} from 'node:sqlite';
import {TextDecoder} from 'node:util';
import {inflateSync} from 'node:zlib';
import {posix} from 'node:path';
import {createHash} from 'node:crypto';
const rows=(db,sql)=>db.prepare(sql).all().map(r=>({...r}));
const failed=(action)=>{try{action();return null;}catch(e){return {code:e.errcode??e.code??e.name};}};

import assert from 'node:assert/strict';
const run=function run(i,corrected=true){
    const db=new DatabaseSync(':memory:');try{db.exec("CREATE TABLE original(id TEXT PRIMARY KEY,quantity INTEGER);INSERT INTO original VALUES('A',1),('B',1);CREATE TABLE shadow(id TEXT PRIMARY KEY,quantity INTEGER NOT NULL CHECK(quantity>0));CREATE TABLE registry(current TEXT);INSERT INTO registry VALUES('original');CREATE VIEW active AS SELECT * FROM original WHERE(SELECT current FROM registry)='original' UNION ALL SELECT * FROM shadow WHERE(SELECT current FROM registry)='shadow';");
      if(corrected)db.exec('BEGIN;');let error=failed(()=>{for(const r of i.candidate)db.prepare('INSERT INTO shadow VALUES(?,?)').run(r.id,r.quantity);});
      if(corrected&&!error){const missing=rows(db,'SELECT id FROM original EXCEPT SELECT id FROM shadow');const extra=rows(db,'SELECT id FROM shadow EXCEPT SELECT id FROM original');if(missing.length||extra.length)error='incomplete-candidate';}
      if(!error||!corrected)db.exec("UPDATE registry SET current='shadow';");if(corrected)db.exec(error?'ROLLBACK;':'COMMIT;');
      return {error,current:db.prepare('SELECT current FROM registry').get().current,active:rows(db,'SELECT * FROM active ORDER BY id'),shadow:rows(db,'SELECT * FROM shadow ORDER BY id')};
    }finally{db.close();}
  };
const cases=[{"label":"misleading base","input":{"candidate":[{"id":"A","quantity":2}]},"expected":{"error":null,"current":"shadow","active":[{"id":"A","quantity":2}],"shadow":[{"id":"A","quantity":2}]},"corrected":false},{"label":"corrected base","input":{"candidate":[{"id":"A","quantity":2}]},"expected":{"error":"incomplete-candidate","current":"original","active":[{"id":"A","quantity":1},{"id":"B","quantity":1}],"shadow":[]},"corrected":true},{"label":"complete candidate commits publication","input":{"candidate":[{"id":"A","quantity":2},{"id":"B","quantity":3}]},"expected":{"error":null,"current":"shadow","active":[{"id":"A","quantity":2},{"id":"B","quantity":3}],"shadow":[{"id":"A","quantity":2},{"id":"B","quantity":3}]},"corrected":true},{"label":"failed candidate write leaves original active","input":{"candidate":[{"id":"A","quantity":2},{"id":"B","quantity":-1}]},"expected":{"error":{"code":275},"current":"original","active":[{"id":"A","quantity":1},{"id":"B","quantity":1}],"shadow":[]},"corrected":true}];
for(const test of cases){
  const actual=run(test.input,test.corrected);
  assert.deepEqual(actual,test.expected,test.label);
  console.log(test.label,actual);
}

下載可執行例子 ↓

下次載入前核邊界

完整 A2/B3 可提交切換；B 負數寫入失敗，shadow 暫建及切換都回復。

可編輯邊界紀錄及預期輸出
情況	輸入 JSON	預期輸出 JSON
候選齊備可提交切換	{"candidate":[{"id":"A","quantity":2},{"id":"B","quantity":3}]}	{"error":null,"current":"shadow","active":[{"id":"A","quantity":2},{"id":"B","quantity":3}],"shadow":[{"id":"A","quantity":2},{"id":"B","quantity":3}]}
候選寫入違限制	{"candidate":[{"id":"A","quantity":2},{"id":"B","quantity":-1}]}	{"error":{"code":275},"current":"original","active":[{"id":"A","quantity":1},{"id":"B","quantity":1}],"shadow":[]}

下載可編輯 CSV ↓

原例候選只有 A，應否成正式資料？

查看參考答案

不應，候選未齊要停，原 A/B 照供使用。完整核過的交易才提交切換。

先核來源與已訂規則

比較兩條實際路徑

下次載入前核邊界

相關資源