9 Commits (16be2fd100199bdf284becfcee02c5eb20d8a11d)

Author	SHA1	Message	Date
Peter Eisentraut	fc946c39ae	Remove useless whitespace at end of lines	15 years ago
Neil Conway	f5ab0a14ea	Add a "USING" clause to DELETE, which is equivalent to the FROM clause ... in UPDATE. We also now issue a NOTICE if a query has _any_ implicit range table entries -- in the past, we would only warn about implicit RTEs in SELECTs with at least one explicit RTE. As a result of the warning change, 25 of the regression tests had to be updated. I also took the opportunity to remove some bogus whitespace differences between some of the float4 and float8 variants. I believe I have correctly updated all the platform-specific variants, but let me know if that's not the case. Original patch for DELETE ... USING from Euler Taveira de Oliveira, reworked by Neil Conway.	21 years ago
Neil Conway	975e27377a	Adjust input routines for float4, float8 and oid to reject the empty string ... as valid input (it was previously treated as 0). This input was deprecated in 8.0 (and a warning was emitted). Regression tests updated.	21 years ago
Neil Conway	e2ded829f6	Revise int2/int4/int8/float4/float8 input routines to allow for ... any amount of leading or trailing whitespace (where "whitespace" is defined by isspace()). This is for SQL conformance, as well as consistency with other numeric types (e.g. oid, numeric). Also refactor pg_atoi() to avoid looking at errno where not necessary, and add a bunch of regression tests for the input to these types.	22 years ago
Neil Conway	2146bfc869	Emit a warning when an empty string is input to the oid, float4, and ... float8 types. This begins the deprecation of this feature: in 7.6, this input will be rejected. Also added a new error code for warnings about deprecated features, and updated the regression tests.	22 years ago
Tom Lane	93fcbd140a	Make oidin/oidout produce and consume unsigned representation of Oid, ... rather than just being aliases for int4in/int4out. Give type Oid a full set of comparison operators that do proper unsigned comparison, instead of reusing the int4 comparators. Since pg_dump is now doing unsigned comparisons of OIDs, it is now *necessary* that we play by the rules here. In fact, given that btoidcmp() has been doing unsigned comparison for quite some time, it seems likely that we have index- corruption problems in 7.0 and before once the Oid counter goes past 2G. Fixing these operators is a necessary step before we can think about 8-byte Oid, too.	25 years ago
Thomas G. Lockhart	61ef6a1a3f	Clean up syntax to use SQL92-ish type coersion ... rather than the Postgres "::" notation. All of these tests have been completely inspected and give correct results.	26 years ago
Marc G. Fournier	3451abf632	Make these self-contained tests...they are testing types, so the tables ... that are created should only exist as long as the test requires them... things are just toooooo spread around	29 years ago
Marc G. Fournier	04688df668	Again, add more tests	29 years ago