Home Search Pricing Get inErrata About

Sign in Sign up

Graph/float-to-int-parameter-mismatch

Pattern

Float-to-Int Parameter Mismatch

float-to-int-parameter-mismatch

Numeric values get implicitly coerced to floating-point (e.g., 20 becomes 20.0 or 1.25 becomes ambiguous 1.2/1.3), so downstream drivers/Cypher/formatters reject or mis-select results, forcing explicit integer/format handling.

Node Details

Public graph metadata

Updated6/26/2026

Connections

30 linked nodes

the component may behave unexpectedly, such as appearing filled with black — If you pass a non-boolean value.

it will display, for example `1029.6`, however I want a dash between then first and second digit — In my database I have an entry for a `NUMERIC(5,1)`. Tension: the number should be 1000<=n<6000. Outcome: how can I do this?

The typemod rounds values above your specified precision. Tension: it complains before the `check` constraint. Outcome: 3333.8.

ERROR: numeric field overflow. Tension: A field with precision 5, scale 1 must round to an absolute value less than 10^4. Outcome: ERROR: numeric field overflow.

always uses period instead of comma as decimal separator — Swift MeasurementFormatter Ignores Custom Locale on CI (GitHub Actions) but Works Locally. Outcome: The problem was setting `locale` in the `NumberFormatter` that's used inside the measurement formatter.

Stripe invoice line item quantity does not support decimal values

In tar's bundled gnulib wordsplit implementation. Tension: the buffer pointer arithmetic uses namelen++ before the copy, creating an off-by-one hazard if namelen/value length relationships ever desynchronize. Outcome: This is flagged by flawfinder as [REDACTED].

related_player_id 12 non-null float64 — trying to load it to a Postgres database. Tension: This has been fine for most of the tables, but the final assignment table is causing me problems. Outcome: bigint out of range.

you get the type mismatch error — merge with PostgreSQL 17.2. Tension: there's no immediate context that could be used to guess its intended type. Outcome: it defaults to `text`.

I get no results — if I turn around and select from this table using this value such as. Tension: The table column seems to have a 6 millisecond precision that the select statement does not reflect. Outcome: It seems like no matter what I do I'm stuck with a precision of 3 millisecond decimal places when selecting.

java.lang.IllegalArgumentException: Can't change resolved type for param: 84 from 2278 to 1700 — if we reach the prepareThreshold. Tension: When the statement is no server side prepared (prepareThreshold is not reached) the SP call works perfectly. Outcome: workaround, it’s based on using CallableStatement#setNull in every out parameter to correct metadata.

TypeError: not enough arguments for format string — template = "%(function)s('(%s) %s-%s', SUBSTRING(%(expressions)s,3,3), SUBSTRING(%(expressions)s,6,3), SUBSTRING(%(expressions)s,9,4))". Tension: I believe it is due to this line `'(%s) %s-%s'` that is supplied to the FORMAT function. Outcome: Yes, you use two consecutive percentages to produce a percentage after formatting.

Buffer overflow cannot be demonstrated reliably

It inconsistently switches between using a hardcoded size and `sizeof`. — char buf[2048]; memset(buf, 0, sizeof(buf)); ... = snprintf(buf, 2048, ...);.

when I want to get the value in a text field or `DatePicker` it does not work fine — I am not able to get value in an input field from a custom component. Tension: The output is like below. Outcome: I suggest converting `DateFormat` to a utility function that returns the computed string value.

This code will compile without an error, and the result — If we change the case for int to use the wrapper class Integer. Tension: Why doesn't Integer dominate byte?

When I change the formula to use LEFT, concatenation of three columns and a fallback value — Apache POI 5.2.5. Tension: the evaluator returns an error. Outcome: result.getErrorValue() == 15 (#VALUE! error).

Java FFM upcall pointer parameters are linked with a confined memory session on Windows when the callback also takes a larger-than-pointer struct

my SQLite Integers into a Java int which only holds 32 bits. Tension: I'd like it to put those values into a long instead.

Why was one of the numbers rounded to 16 precision while the other was rounded to 17? — System.out.printf("x = %.20f , y = %.20f%n", x, y);. Tension: Why aren't they both 16 precision? Or why aren't they both 17 precision? Outcome: why the precisions are different?

java: incompatible types: possible lossy conversion from short to byte — byte r = true ? x : y;.

datetime(3) values lose trailing .000 fractional seconds when read back, breaking parsing

the condition doesn't seem to trigger as expected — when the stored value is null. Tension: I need to check the type of the object to handle null values differently for Integer and String. Outcome: it always falls through to returning null.

I don't understand when the very last disambiguation (using `round_to_nearest`) would actually happen. — If there are several such representations, the representation with the smallest difference from the floating-point argument value is chosen. Tension: I don't understand when the very last disambiguation (using `round_to_nearest`) would actually happen. Outcome: These examples are hypothetical, but they show when th.

fails, as the compiler outsmarts me by using the 32-bit version instead — Using the most straightforward approach.

DMCAModel IntegerField ratio is rejected when blank=True, null=True, default=None

one-byte heap buffer over-read (CVE-2022-48303) in its base-256 (binary) numeric field decoder — GNU tar 1.34 (src/list.c, function `from_header`). Outcome: unbounded heap over-reads until an overflow check or segfault.

integer underflow vulnerability in the search_impl function — When searching backward for a pattern within a string. Tension: the calculation of the remaining 'post' substring size uses a flawed formula. Outcome: This leads to memory corruption when the oversized substring is later accessed.

passing limit: 20 over the Bolt protocol sends 20.0 which Neo4j rejects — Neo4j Cypher parameters like LIMIT and maxLevel require integer values. Tension: This breaks any Cypher query with integer params when called from JS without explicit integer wrapping.

contains an integer overflow vulnerability in the bitshift operator (PtCr_bitshift) — The PostScript Type 4 Calculator function in Ghostscript (versions through 9.52). Tension: The bounds check for the shift operand is off-by-one, allowing shift amounts that exceed the safe range for signed integers. Outcome: potentially leading to memory corruption, heap overflow, or code execution.

[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

Float-to-Int Parameter Mismatch - inErrata Knowledge Graph | Inerrata