匯入回復後，剛核過的行為何消失？

先核來源與已訂規則

本例正式採用須一行已提交 A。同一連線在 BEGIN 內計數可見新行，即使之後整次回復。更正要提交或回復後才核，並須真正提交成功且有所需行。

已填假設輸入
紀錄	輸入 JSON
原例輸入	{"insert":true,"commit":false}

下載可編輯 CSV ↓

比較兩條實際路徑

錯結果報已採用、數 1，但最後目標空。更正已回復結果應數 0、未採用。

錯誤與更正路徑的輸出
路徑	輸出 JSON
錯誤路徑	{"released":true,"verifiedCount":1,"target":[]}
更正路徑	{"released":false,"verifiedCount":0,"target":[]}

下載可編輯 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 target(id TEXT PRIMARY KEY);BEGIN;');if(i.insert)db.exec("INSERT INTO target VALUES('A');");
      const before=db.prepare('SELECT COUNT(*) AS n FROM target').get().n;db.exec(i.commit?'COMMIT;':'ROLLBACK;');
      const target=rows(db,'SELECT * FROM target');const verifiedCount=corrected?target.length:before;
      return {released:corrected?i.commit&&verifiedCount===1:verifiedCount===1,verifiedCount,target};
    }finally{db.close();}
  };
const cases=[{"label":"misleading base","input":{"insert":true,"commit":false},"expected":{"released":true,"verifiedCount":1,"target":[]},"corrected":false},{"label":"corrected base","input":{"insert":true,"commit":false},"expected":{"released":false,"verifiedCount":0,"target":[]},"corrected":true},{"label":"successful commit evidence","input":{"insert":true,"commit":true},"expected":{"released":true,"verifiedCount":1,"target":[{"id":"A"}]},"corrected":true},{"label":"commit alone does not prove required row","input":{"insert":false,"commit":true},"expected":{"released":false,"verifiedCount":0,"target":[]},"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);
}

下載可執行例子 ↓

下次載入前核邊界

成功提交會留 A；只提交空交易，不能證明有所需紀錄。

可編輯邊界紀錄及預期輸出
情況	輸入 JSON	預期輸出 JSON
提交成功且有所需行	{"insert":true,"commit":true}	{"released":true,"verifiedCount":1,"target":[{"id":"A"}]}
提交但欠所需行	{"insert":false,"commit":true}	{"released":false,"verifiedCount":0,"target":[]}

下載可編輯 CSV ↓

交易內行數可確認此次已回復匯入成功嗎？

查看參考答案

不可，那是暫時狀態。最後已提交狀態查到零行，須擋正式採用。

先核來源與已訂規則

比較兩條實際路徑

下次載入前核邊界

相關資源