Consider the following example:

<pre>
CREATE TABLE t0 (c0 TEXT);
INSERT INTO t0(c0) VALUES ('1.0');
SELECT CAST(c0 AS NUMERIC) FROM t0; -- expected: 1, actual: 1.0
</pre>

From the following part of the documentation, I would expect that the the value '1.0' is converted to 1:

<pre>
Casting a TEXT or BLOB value into NUMERIC first does a forced conversion into REAL but then further converts the result into INTEGER if and only if the conversion from REAL to INTEGER is lossless and reversible.
</pre>

I remember that this previously worked as I would expect. Could this be a regression caused by [67a68af5578f08d2]?