BestHub
Sign in
Tagged articles
24 articles
Page 1 of 1
Java Architect Essentials
Java Architect Essentials
Mar 23, 2026 · Databases

When MySQL Auto‑Increment Hits Its Limit: Diagnosis and Fixes

A backend engineer discovers that a massive MySQL table’s auto‑increment INT primary key reached its maximum value, causing insert failures, and walks through detailed analysis, three remediation options—including switching to BIGINT, redesigning IDs, and sharding—plus practical scripts, performance measurements, and lessons learned about concurrency and schema design.

BIGINTauto_incrementconcurrency
0 likes · 10 min read
When MySQL Auto‑Increment Hits Its Limit: Diagnosis and Fixes
dbaplus Community
dbaplus Community
Jan 3, 2026 · Databases

When MySQL Auto‑Increment Hits INT Limit: Diagnosis and Fixes

The article recounts a MySQL production incident where an INT auto‑increment column reached its maximum value, causing insert failures, and walks through analysis, three remediation options, a stored‑procedure cleanup, a conversion to BIGINT, performance monitoring, and lessons on concurrency and schema design.

BIGINTDatabase PerformanceINT overflow
0 likes · 9 min read
When MySQL Auto‑Increment Hits INT Limit: Diagnosis and Fixes
Architect
Architect
Oct 30, 2025 · Databases

When MySQL Auto‑Increment IDs Hit Their Limit: Diagnosis and Fixes

A massive MySQL table ran out of INT auto‑increment IDs due to high concurrency, leading to insert failures; the article analyzes the root cause, evaluates three remediation strategies, and details the eventual migration to BIGINT with performance monitoring and code snippets.

BIGINTauto_incrementconcurrency
0 likes · 9 min read
When MySQL Auto‑Increment IDs Hit Their Limit: Diagnosis and Fixes
Java Tech Enthusiast
Java Tech Enthusiast
Oct 7, 2025 · Databases

When MySQL Auto‑Increment Hits INT Limit: Diagnosis & Fixes

The article recounts a real‑world incident where a massive MySQL table exceeded the INT auto‑increment limit, causing insert failures, and walks through analysis, three remediation strategies—including converting to BIGINT, using distributed IDs, and sharding—plus practical SQL scripts and performance insights for handling billions of rows.

BIGINTINT overflowauto_increment
0 likes · 9 min read
When MySQL Auto‑Increment Hits INT Limit: Diagnosis & Fixes
macrozheng
macrozheng
Aug 11, 2025 · Databases

Why MySQL Auto‑Increment IDs Hit Their Limit and How to Fix It

This article recounts a real‑world MySQL incident where the auto‑increment INT overflowed after billions of rows, explores why the ID limit was reached, evaluates three remediation strategies—including switching to BIGINT, distributed IDs, and sharding—and shares practical SQL scripts and performance insights.

BIGINTStored Procedureauto_increment
0 likes · 9 min read
Why MySQL Auto‑Increment IDs Hit Their Limit and How to Fix It
Architecture Digest
Architecture Digest
Jul 21, 2025 · Databases

When MySQL Auto‑Increment IDs Hit Their Limit: Diagnosis and Fixes

A massive MySQL table reached the INT auto‑increment ceiling, causing insert failures; the article details how the issue was identified, explores three remediation strategies—including converting the column to BIGINT, redesigning IDs, and sharding—shows stored‑procedure scripts, performance monitoring, and practical lessons on schema design and multithreaded batch processing.

BIGINTauto_incrementmysql
0 likes · 8 min read
When MySQL Auto‑Increment IDs Hit Their Limit: Diagnosis and Fixes
Top Architect
Top Architect
Jul 20, 2025 · Databases

When MySQL Auto‑Increment IDs Hit Their Limit – Diagnosis and Fixes

A senior architect investigates a missing device error caused by MySQL auto‑increment IDs reaching the 32‑bit integer limit, analyzes the overflow issue, evaluates three remediation strategies—including converting the column to BIGINT, adopting distributed IDs, or sharding the database—and shares practical code snippets and performance insights for large‑scale data migrations.

BIGINTauto_incrementdatabase migration
0 likes · 11 min read
When MySQL Auto‑Increment IDs Hit Their Limit – Diagnosis and Fixes
ITPUB
ITPUB
Jun 27, 2025 · Fundamentals

Why Does num === num - 1 Sometimes Return True in JavaScript?

This article explains the special cases where the JavaScript expression num === num - 1 evaluates to true, covering Infinity, numbers beyond the safe integer range, how to detect unsafe values, and practical solutions using Number.isSafeInteger, BigInt, bignumber.js, and a custom big‑integer addition implementation.

Arbitrary PrecisionBIGINTInfinity
0 likes · 8 min read
Why Does num === num - 1 Sometimes Return True in JavaScript?
Architect
Architect
May 17, 2025 · Databases

Storing 2 Billion Phone Numbers: Why VARCHAR(20) Is Preferable to INT/BIGINT

The article explains why using a VARCHAR(20) column to store billions of phone numbers is safer and more flexible than INT or BIGINT, covering range limits, data integrity, query convenience, interview expectations, and common pitfalls such as insufficient field length, charset issues, missing indexes, and lack of encryption.

BIGINTdata integrityphone number storage
0 likes · 10 min read
Storing 2 Billion Phone Numbers: Why VARCHAR(20) Is Preferable to INT/BIGINT
Java Tech Enthusiast
Java Tech Enthusiast
Apr 30, 2025 · Databases

Storing 2 Billion Phone Numbers: Int vs String, Schema Design and Pitfalls

When designing a schema for two‑billion phone numbers, use a VARCHAR(20) column with utf8mb4 Unicode, a unique index, and proper validation/encryption rather than a 32‑bit INT, because strings preserve leading zeros, international prefixes, extensions, and support business extensibility, fault tolerance, and future changes.

BIGINTDatabase designdata type selection
1 likes · 7 min read
Storing 2 Billion Phone Numbers: Int vs String, Schema Design and Pitfalls
Rare Earth Juejin Tech Community
Rare Earth Juejin Tech Community
Feb 5, 2024 · Frontend Development

Lesser‑Known but Useful ES6 Features and Techniques

This article introduces several relatively obscure yet practical ES6 features—including Object.entries/Object.fromEntries, Symbol, WeakMap/WeakSet, Promise.allSettled, BigInt, Array.of/Array.from, and the .at and flat methods—explaining their purpose and providing code examples for each.

ArrayBIGINTJavaScript
0 likes · 8 min read
Lesser‑Known but Useful ES6 Features and Techniques
Laravel Tech Community
Laravel Tech Community
Mar 8, 2021 · Databases

Understanding MySQL AUTO_INCREMENT Limits and Best Practices

This article explains MySQL AUTO_INCREMENT behavior, demonstrates creating tables with unsigned int primary keys, shows how to set and inspect the AUTO_INCREMENT value, discusses its maximum limits, and recommends using bigint or explicit primary keys to avoid overflow and duplicate‑key errors.

BIGINTDatabase designauto_increment
0 likes · 4 min read
Understanding MySQL AUTO_INCREMENT Limits and Best Practices
macrozheng
macrozheng
Jan 27, 2021 · Databases

When MySQL Auto‑Increment IDs Hit Their Limit: Errors and Fixes

This article explains how MySQL integer auto‑increment primary keys can reach their maximum value, the resulting duplicate‑key errors, and how using BIGINT or understanding InnoDB's internal row_id behavior can prevent data loss or crashes.

BIGINTDatabase Limitsauto_increment
0 likes · 6 min read
When MySQL Auto‑Increment IDs Hit Their Limit: Errors and Fixes
Sohu Tech Products
Sohu Tech Products
Oct 21, 2020 · Frontend Development

Key New Features of ES2020 (ES11): Private Fields, Promise.allSettled, BigInt, Nullish Coalescing, Optional Chaining, Dynamic Import, matchAll, globalThis, and Module Namespace Exports

This article reviews the most useful ES2020 (ES11) JavaScript features—including private class fields, Promise.allSettled, the BigInt type, nullish coalescing (??), optional chaining (?.), dynamic import, String.prototype.matchAll, globalThis, and module namespace exports—explaining their syntax, behavior, and practical code examples.

BIGINTDynamicImportES2020
0 likes · 12 min read
Key New Features of ES2020 (ES11): Private Fields, Promise.allSettled, BigInt, Nullish Coalescing, Optional Chaining, Dynamic Import, matchAll, globalThis, and Module Namespace Exports
Qunar Tech Salon
Qunar Tech Salon
Dec 5, 2019 · Frontend Development

Evolution of JavaScript: From Prototype Methods to Async/Await and Modern Features

This article traces JavaScript’s evolution, covering the enrichment of prototype methods, standardization of classes and modules, the rise of asynchronous patterns like callbacks, promises, generators, async/await, and modern syntax features such as block scope, symbols, BigInt, reflection, and useful syntactic sugar.

AsyncBIGINTGenerators
0 likes · 28 min read
Evolution of JavaScript: From Prototype Methods to Async/Await and Modern Features
Java Backend Technology
Java Backend Technology
Apr 26, 2019 · Databases

What Happens When MySQL Auto‑Increment IDs Exhaust? Practical Solutions

This article explains why MySQL auto‑increment primary keys can reach their limit, shows how switching from INT to BIGINT prevents overflow, and reviews three online schema‑change methods—including native ALTER, pt‑osc, and gh‑ost—plus considerations for triggers, foreign keys, and master‑slave setups.

BIGINTOnline Schema Changeauto_increment
0 likes · 8 min read
What Happens When MySQL Auto‑Increment IDs Exhaust? Practical Solutions
Node Underground
Node Underground
Nov 23, 2018 · Backend Development

What’s New in Node.js 10 LTS? Key Features, Deprecations, and Experimental APIs

Node.js 10 LTS introduces major updates such as native HTTP/2 support, BigInt, recursive directory creation, CLI flag auto‑completion, Windows installer improvements, V8‑based code coverage, deprecated Buffer constructors, and experimental Worker Threads, while also upgrading OpenSSL and adding PEM‑level encryption.

BIGINTHTTP/2LTS
0 likes · 11 min read
What’s New in Node.js 10 LTS? Key Features, Deprecations, and Experimental APIs