Insert too-large double produces wrong exception via Postgres
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Akiban SQL Parser |
Confirmed
|
Low
|
Unassigned |
Bug Description
Using the Postgres server to insert a too-large value produces a parse
exception rather than an overflow exception (error code 42000
vs. 55004).
Note that it is also unclear why this overflow should produce an
exception when integer overflows are truncated.
SQL:
CREATE TABLE t (double_field double)
INSERT INTO t VALUES (1.797693134862
Result:
org.postgresq
at org.postgresql.
at org.postgresql.
at org.postgresql.
at org.postgresql.
at org.postgresql.
at org.postgresql.
at com.akiban.
... 44 more
To reproduce:
mvn test -Dtest=
Reproduced in trunk revision 1239
Changed in akiban-sql-parser: | |
milestone: | none → future |
importance: | Undecided → Low |
tags: | added: types |
information type: | Private → Public |
Since it is not possible to store a Double literal of this value, this probably requires a more specific Exception from the parser itself.