[{"data":1,"prerenderedAt":189},["ShallowReactive",2],{"page:/zh-TW/guides/year-2038-problem":3},{"id":4,"title":5,"body":6,"description":175,"extension":176,"eyebrow":177,"faq":178,"locale":179,"meta":180,"navigation":181,"pageType":182,"path":183,"related":178,"seo":184,"stem":187,"__hash__":188},"pages/zh-TW/guides/year-2038-problem.md","2038 年問題",{"type":7,"value":8,"toc":163},"minimark",[9,14,23,27,30,34,37,41,44,47,97,106,109,112,115,118,121,129,141,144],[10,11,13],"h2",{"id":12},"邊界在哪裡","邊界在哪裡？",[15,16,17,18,22],"p",{},"32 位元有號整數範圍是 −2,147,483,648 到 2,147,483,647。解讀成 Unix 秒時，正數上限對應 ",[19,20,21],"code",{},"2038-01-19T03:14:07Z","；再加一秒就會在這種表示中溢位。",[10,24,26],{"id":25},"哪些系統需要檢查","哪些系統需要檢查？",[15,28,29],{},"舊作業系統、嵌入式裝置、資料庫欄位和二進位協定仍可能使用 32 位元有號秒。64 位元時間戳或合適的日期類型能把實際邊界推到一般應用程式壽命之外，但必須確認完整資料鏈路都已升級。",[10,31,33],{"id":32},"如何測試","如何測試？",[15,35,36],{},"應在邊界兩側選取數值，穿過解析器、儲存、API 序列化、用戶端執行環境和報表工具進行端到端測試。現代應用伺服器無法自動保護舊資料庫欄位或裝置協定。",[10,38,40],{"id":39},"不只看-2038-年","不只看 2038 年",[15,42,43],{},"也要檢查毫秒欄位的整數範圍、JavaScript 安全整數與第三方 API 的日期限制。不同單位與類型可能在不同年份到達邊界。",[10,45,46],{"id":46},"上限附近的三個數值",[48,49,50,63],"table",{},[51,52,53],"thead",{},[54,55,56,60],"tr",{},[57,58,59],"th",{},"Unix 秒",[57,61,62],{},"UTC 日期",[64,65,66,77,87],"tbody",{},[54,67,68,74],{},[69,70,71],"td",{},[19,72,73],{},"2147483646",[69,75,76],{},"2038-01-19 03:14:06",[54,78,79,84],{},[69,80,81],{},[19,82,83],{},"2147483647",[69,85,86],{},"2038-01-19 03:14:07",[54,88,89,94],{},[69,90,91],{},[19,92,93],{},"2147483648",[69,95,96],{},"2038-01-19 03:14:08",[15,98,99,100,105],{},"第三個值本身合法，只是超過帶正負號 32 位元整數的容量，並非 Unix 時間結束。可在",[101,102,104],"a",{"href":103},"/zh-TW/timestamp-to-date/","時間戳轉日期工具","手動選擇秒核對。",[15,107,108],{},"這類整數範圍為 −2,147,483,648 至 2,147,483,647。舊系統若溢位回繞而非拒絕寫入，下個值可能變成負數，顯示到 1901 年。實際行為取決於語言、作業系統與儲存方式。",[10,110,111],{"id":111},"不只檢查資料庫欄位",[15,113,114],{},"檢查資料庫欄位、驅動程式、API 型別、序列化與應用變數。只擴大資料庫欄位，無法處理客戶端或嵌入式裝置仍強制轉成 32 位元整數的問題。測試邊界兩側，寫入後讀回並核對整數，不能只看格式化日期。",[15,116,117],{},"選擇整條資料路徑支援的寬整數或日期型別。無正負號的 32 位元秒數雖有較晚的上限，但不支援負日期，也未解決所有協定限制。",[10,119,120],{"id":120},"與其他數值限制分開看",[15,122,123,124,128],{},"2038 問題針對帶正負號 32 位元的",[125,126,127],"strong",{},"秒","。JavaScript 安全整數上限與瀏覽器日期範圍是其他限制。同一時刻的毫秒、微秒、奈秒數值更大，不能因為還沒到 2038 就認為精度安全。",[15,130,131,135,136,140],{},[101,132,134],{"href":133},"/zh-TW/guides/seconds-vs-milliseconds/","秒與毫秒指南","說明單位；",[101,137,139],{"href":138},"/zh-TW/batch-converter/","批次轉換器","可檢查遷移檔案日期，但無法檢查或修改外部系統的資料型別。",[10,142,143],{"id":143},"標準與執行環境參考",[145,146,147,156],"ul",{},[148,149,150],"li",{},[101,151,155],{"href":152,"rel":153},"https://man7.org/linux/man-pages/man2/time.2.html",[154],"nofollow","Linux time(2)",[148,157,158],{},[101,159,162],{"href":160,"rel":161},"https://tc39.es/ecma262/multipage/numbers-and-dates.html#sec-time-values-and-time-range",[154],"ECMAScript Date time range",{"title":164,"searchDepth":165,"depth":165,"links":166},"",2,[167,168,169,170,171,172,173,174],{"id":12,"depth":165,"text":13},{"id":25,"depth":165,"text":26},{"id":32,"depth":165,"text":33},{"id":39,"depth":165,"text":40},{"id":46,"depth":165,"text":46},{"id":111,"depth":165,"text":111},{"id":120,"depth":165,"text":120},{"id":143,"depth":165,"text":143},"了解 32 位元有號 Unix 秒為何在 2038 年 1 月溢位、哪些系統受影響及如何安全檢查。","md","指南 / 邊界",null,"zh-TW",{},true,"guide","/zh-tw/guides/year-2038-problem",{"title":185,"description":186},"2038 年問題詳解 — Unix 時間戳上限","理解 32 位元有號 Unix 時間戳在 2038-01-19 的邊界，以及現代 64 位元系統如何避開限制。","zh-TW/guides/year-2038-problem","cunXwzyF2C5WhYRmonarw-n0ShxDiqkfVPp9L63Podo",1792032486443]