0 views collected around this technical thread.
This article explains why the number in MySQL's int(N) definition does not limit the column's numeric range, demonstrates that int(1) can store the full 4‑byte unsigned range, and shows how the ZEROFILL attribute adds zero‑padding for display purposes.
This article examines why storing phone numbers as Java Strings rather than ints yields better memory usage, semantic correctness, and JVM-level performance, discussing primitive vs reference types, bytecode differences, string pooling, and real‑world case studies.
Because phone numbers are identifiers that can contain symbols and exceed the numeric range of an int, storing them as a String—despite higher memory use—is semantically correct, avoids overflow, preserves formatting, and benefits from JVM string pooling, making String the preferred type in most Java applications.
The article examines the trade‑offs of using Java's primitive int versus the String class to store phone numbers, covering memory usage, JVM bytecode behavior, data semantics, and practical performance implications for large‑scale systems.
While storing early five‑ and six‑digit QQ IDs as int32 or int64 offers memory efficiency and fast queries, the later expansion to eleven‑digit numbers and potential inclusion of non‑numeric symbols makes a string representation preferable to ensure flexible, future‑proof handling of QQ numbers.
This article explains that the numeric argument in MySQL int types does not restrict the stored range, demonstrates inserting the maximum unsigned int value, and shows how combining a display width with ZEROFILL pads numbers with leading zeros for formatted output.
This article explains Python's special (magic) methods such as __bool__, __int__, __float__, __complex__, __index__, __oct__, __hex__, and __dir__, describing their purpose, how they affect object behavior, and provides concrete code examples demonstrating their usage and output.
This article explains why MySQL columns defined as INT(10) appear as INT after upgrading from 5.7 to 8.0, demonstrates the change with reproducible examples, and discusses the storage limits, proper selection, and display‑width behavior of integer types including ZEROFILL.
This article explains how to use Python's built‑in casting functions—int(), float(), str(), bool(), list(), tuple(), set() and dict()—to convert between numeric, string, boolean, sequence, and mapping types, providing clear code examples for each conversion scenario.
This article explains that the numeric value in MySQL INT definitions (e.g., int(1) or int(10)) does not limit the column's range, demonstrates inserting the maximum unsigned value, and shows how ZEROFILL combined with a display width pads numbers with leading zeros.
The article explains that the number in MySQL's INT definition (e.g., INT(1) or INT(4)) does not limit the column's numeric range, but only affects display width when combined with ZEROFILL, illustrating the concept with practical CREATE and INSERT examples.
This article introduces Python’s fundamental data types—including integers, floats, booleans, and strings—explaining their characteristics, representation formats, common pitfalls such as floating‑point precision, and provides concise code examples illustrating each type’s usage in Python.