summaryrefslogtreecommitdiff
path: root/src/test/regress/expected/lseg.out
AgeCommit message (Collapse)Author
2023-02-27Rework pg_input_error_message(), now renamed pg_input_error_info()Michael Paquier
pg_input_error_info() is now a SQL function able to return a row with more than just the error message generated for incorrect data type inputs when these are able to handle soft failures, returning more contents of ErrorData, as of: - The error message (same as before). - The error detail, if set. - The error hint, if set. - SQL error code. All the regression tests that relied on pg_input_error_message() are updated to reflect the effects of the rename. Per discussion with Tom Lane and Andrew Dunstan. Author: Nathan Bossart Discussion: https://postgr.es/m/[email protected]
2022-12-14Convert the geometric input functions to report errors softly.Tom Lane
Convert box_in, circle_in, line_in, lseg_in, path_in, point_in, and poly_in to the new style. line_in still throws hard errors for overflows/underflows that can occur when the input is specified as two points rather than in the canonical "Ax + By + C = 0" style. I'm not too concerned about that: it won't be reached in normal dump/restore cases, and it's fairly debatable that such conversion should ever have been made part of a type input function in the first place. But in any case, I don't want to extend the soft error conventions into float.h without more discussion than this patch has had. Amul Sul, minor mods by me Discussion: https://postgr.es/m/CAAJ_b97KeDWUdpTKGOaFYPv0OicjOu6EW+QYWj-Ywrgj_aEy1g@mail.gmail.com
2018-09-26Improve test coverage of geometric typesTomas Vondra
This commit significantly increases test coverage of geo_ops.c, adding tests for various issues addressed by 2e2a392de3 (which went undetected for a long time, at least partially due to not being covered). This also removes alternative results expecting -0 on some platforms. Instead the functions are should return the same results everywhere, transforming -0 to 0 if needed. The tests are added to geometric.sql file, sorted by the left hand side of the operators. There are many cross datatype operators, so this seems like the best solution. Author: Emre Hasegeli Reviewed-by: Tomas Vondra Discussion: https://www.postgresql.org/message-id/CAE2gYzxF7-5djV6-cEvqQu-fNsnt%3DEqbOURx7ZDg%2BVv6ZMTWbg%40mail.gmail.com
2008-09-01Add a bunch of new error location reports to parse-analysis error messages.Tom Lane
There are still some weak spots around JOIN USING and relation alias lists, but most errors reported within backend/parser/ now have locations.
2003-09-25Message editing: remove gratuitous variations in message wording, standardizePeter Eisentraut
terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
2003-07-27Error message editing in utils/adt. Again thanks to Joe Conway for doingTom Lane
the bulk of the heavy lifting ...
2000-01-05Verified output from new psql.Thomas G. Lockhart
Include a few new tests for datetime/timespan arithmetic.
1998-02-11Update test for newly implemented "<=" operator.Thomas G. Lockhart
1998-01-10Fix up for recent changes in elog error messages.Thomas G. Lockhart
Some behavior of the triggers test cases changed for the least week or two; now back to the usual expected behavior.
1998-01-06Regression cleanup of WARN.Bruce Momjian
1998-01-05Change elog(WARN) to elog(ERROR) and elog(ABORT).Bruce Momjian
1997-07-29Results from initial changes to add new functions and for bug fixes.Thomas G. Lockhart
Not all cleaned up yet.
1997-05-11Add inter-type regression tests for geometry, date/time, and numbers.Thomas G. Lockhart
Add regression tests for circles, line segments, and paths. Modify regression tests to allow GEQ optimizer (order results).