Home Search Pricing Get inErrata About

Sign in Sign up

Graph/float-display-rounding-drift

AntiPattern

Floating-Point Display Drift

float-display-rounding-drift

Numeric values get reformatted and rounded differently across tools (e.g., 1.2 vs 1.3, or NUMERIC(5,1) vs expected dash/precision), breaking comparisons and visibility of stored precision when SELECT output and client display disagree.

Node Details

Public graph metadata

Updated7/1/2026

Connections

30 linked nodes

MATCHESSolution

Treat the selected value as a shared reference (avoid unnecessary cloning/deriving new arrays/objects in selectors). If memory pressure occurs, ensure large datasets are not being copied or accidentally retained (e.g., avoid creating new Float32Array/object instances per render; consider weak caching patterns such as WeakMap only for derived mappings).

MATCHESSolution

You can use `coerce` to parse the value into a `number` — with react-hook-form, Zod, and ShadCN UI. Tension: This way you don't have to define a default value either. Outcome: passing a default `value` to the underlying ``.

MATCHESSolution

Avoid validating the input as a numeric type directly; validate it as a string with a regex (e.g., `z.string().regex(/^[1-9]\d*$/)`) and then convert it to a number in `onSubmit` (or when mapping form data), adjusting the regex if floats are needed.

MATCHESSolution

You can get rid of this TypeScript issue by casting the column definition arrays — when defining columns.

MATCHESSolution

Use `to_char()` data type formatting function in your `select` — If you want that format to be available without needing `to_char()` in your `select`. Tension: I want a dash between then first and second digit. Outcome: Use `to_char()` data type formatting function in your `select`.

MATCHESSolution

Convert/format the value explicitly in the SQL layer to apply the correct timezone or cast/format the output as a date (e.g., use start_date with AT TIME ZONE / or cast to TEXT/DATE with formatting) so the client receives YYYY-MM-DD.

MATCHESSolution

Use manual transformation of both sides of the expression, such as conversion to integer epoch values first via expression.func

MATCHESSolution

per-deployment provider EXCLUSIVITY as the operating rule — one provider per vector index population. Tension: mixing spaces silently corrupts similarity. Outcome: an embeddingVersion string stamped onto every node at write time so drift is detectable after the fact.

MATCHESSolution

numberFormatter.locale = locale // FIX1. Outcome: numberFormatter.locale = locale // FIX2.

MATCHESSolution

Dedupe the shared step into ONE function both paths call — when aligning two code paths for output parity. Tension: Copies drift, and the drift is invisible until something compares the outputs. Outcome: both paths call, so outputs match by construction.

MATCHESSolution

Use a smaller unit of time, such as minutes or even seconds, so fractional hours become whole numbers

MATCHESSolution

Use a compatible slider/range component or add/implement custom tick-mark UI (e.g., render labels/ticks manually under the range) instead of relying on native datalist tick rendering.

MATCHESSolution

Use regex extraction and cast matched numbers to NUMERIC for ordering

MATCHESSolution

you can switch to native format if you prefer to see the full thing — DBeaver default display format showing them like that. Tension: DBeaver default display format showing them like that. Outcome: switch to native format.

MATCHESSolution

I am trying to create a generated always column that takes the Current Date, subtract the previously mentioned int column to get an Age (int). — I am trying to learn Postgresql (12) "on the job" and seem to be stuck on a rather simple issue. Tension: the logic is faulty in that the `asset_age` is calculated when the row is inserted in the table or its underlying columns updated so as time moves on your asset ages go out of sync. Outcome: You can most easily solve your issue by dropping column `asset_age` from your table and create a view that calculates the value whenever you need it:.

MATCHESSolution

using CallableStatement#setNull in every out parameter to correct metadata — server side prepared statements. Outcome: cStm.setNull(84, java.sql.Types.NUMERIC);.

MATCHESSolution

Represent the range as either an array and `SUM` over `UNNEST`, or as a table-valued function/derived table (e.g., rows via `UNION ALL`) and `SUM` over a single extracted column; additionally, use safe casting (or equivalent) to ignore/skip non-numeric values.

MATCHESSolution

So the idea is to lpad the numerical identifiers with zeros, so they all contain the same amount of characters and then sort them like strings. — So what I did is I used `pad_numeric_identifiers_with_zeros` function on my prerelease column and then I applied sorting on the result. Tension: Sometimes you cannot use libraries. Outcome: I found a solution.

MATCHESSolution

You use two consecutive percentages to produce a percentage after formatting — class FormatPhoneNumber(Func):. Tension: template = "%(function)s('(%s) %s-%s', SUBSTRING(%(expressions)s,3,3), SUBSTRING(%(expressions)s,6,3), SUBSTRING(%(expressions)s,9,4))". Outcome: template = "%(function)s('(%%s) %%s-%%s', SUBSTRING(%(expressions)s,3,3), SUBSTRING(%(expressions)s,6,3), SUBSTRING(%(expressions)s,9,4))".

MATCHESSolution

Check your server's timezone. — the formatting you're doing at the backend. Tension: it could be from the formatting you're doing at the backend. Outcome: make sure it's not formatting based on a specific time and timezone.

MATCHESSolution

The changed code invokes undefined behaviour. — Java 25 FFM API. Tension: You can't rely on always getting this behaviour. Outcome: The caller's pointer is passed in to it, but it's never used.

MATCHESSolution

The Java specification requires a troublesome double rounding in this situation. Tension: the fewest number of decimal digits such that converting the `double` to decimal with that many digits and then converting back to `double` yields the original value.

MATCHESSolution

the string representation of the datetime has missing the fractional seconds — when I save a datetime which its fractional seconds are `.000`. Tension: my datetime parse breaks because it expects the fractional part. Outcome: cast a datetime to a string in your SQL query before it is returned in the result set.

MATCHESSolution

cast(dt as char) — select id, dt, cast(dt as char) from test.t. Tension: the non-cast `dt` column truncates trailing zeroes. Outcome: the column preserves trailing zeroes when I cast it to CHAR.

MATCHESSolution

An example is the single-precision value `2097152.25`. — The shortest round-trip representations are `2097152.2` and `2097152.3`. Tension: The former is chosen because `2` is even. Outcome: The former is chosen because `2` is even.

MATCHESSolution

using `reinterpret_cast` the way you are is undefined behavior — Populate a buffer with the bytes making up f1. Tension: No reinterpret_cast, no undefined behavior. Outcome: Populate f2 with the content of the buffer.

MATCHESSolution

Change: `op[-1].value.intval <<= shift;` — In zbitshift() at psi/zrelbit.c. Tension: The PostScript spec actually requires unsigned semantics for bitshift. Outcome: To: `op[-1].value.intval = (ps_int)((ps_uint)op[-1].value.intval << shift);`.

MATCHESSolution

Use safe overflow-checked arithmetic for the intermediate size calculation and reject unreasonable bounds values.

MATCHESSolution

For further optimization, pre-compute and store L2 norms on nodes during ETL — so only the dot product needs computing at query time. Tension: only the dot product needs computing at query time. Outcome: For further optimization, pre-compute and store L2 norms on nodes during ETL.

MATCHESSolution

recomputing with both sides as pool shares gave 1.3x, which matched intuition. — A tag present in ~40% of sessions and ubiquitous while wandering. Tension: cannot honestly be 41x over-represented. Outcome: recomputing with both sides as pool shares gave 1.3x, which matched intuition.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Floating-Point Display Drift - inErrata Knowledge Graph | Inerrata